Access application gets full screen on double click from taskbar button - vba

I developed a tool in MS Access where I hide the top pane of Access so that user can only close the application by clicking close button on the pop up form. That leaves no way for the user to minimize or restore Access window as is required.
However, the problem comes when a user clicks the Acess button twice from the taskbar on windows 10, it gets into full screen mode and user cannot restore it unless by closing and reopening the application. Can someone please provide a solution to this?

Related

How to keep MS Access Forms only in the MS Access Window/Canvas?

I have created my MS Access Program but I have multiple monitors and so do the other people who will be using the program.
Just so you know my forms are popup style, have no borders or record selectors and I am guessing this is where my issue comes in.
I would like to know if there is a way to ensure that when a user opens a form, the form will only open within the MS Access Window/Canvas on the active monitor?
I would also like to know if there is a way for my application to automatically adjust according to the users screen resolution?
As an example my Forms open perfectly when I am using the application on my main screen which has a resolution of 3840 x 2160 but if I open the application on my second screen which has a resolution of 1920 x 1080 the forms that open subsequently, such as the user form, then opens on the main screen so small that no one can read or see it.
Application is on Right monitor and User Form is Open on Left (Main) Monitor
The code I have used for the OnOpen Event is below:
Private Sub Form_Open(Cancel As Integer)
Dim Right As Integer, Down As Integer
Right = Screen.ActiveForm.WindowLeft
Down = Screen.ActiveForm.WindowTop
DoCmd.MoveSize Right, Down
End Sub
This was obtained from some research but I cant seem to bind everything to the Application Window/Canvas.
Thank you.
Well, if you only ever have one window open at one time, then you can do this with ease.
Remember, today most applications are SPA (what we call single page applications). We don't use (nor have) very often a main applcation window, and THEN a child window. For one, they tend to not be touch friendly, and it is VERY hard to move a window around with touch.
but, even desktop browsers even use some "kind" of tabbed interface. And so do most desktop applications. And by tabbed - I don't necessary mean across the top. This access screen shows a tab system from the left side:
So, Access now has a option to use tabbed interface.
And if you :
do NOT use pop windows.
Set access to use tabbed interface, eg this:
Then un-check the display tabs.
If you do above, then you WILL NEVER EVER see the access background window.
You see this:
However, keep this in mind:
The form you launch will re-size to the main size of the Access window - not the other way around.
All forms can't be popup
You are "SPA" like applcation.
So, most accounting and most desktop applications now work this way. And WHEN you launch a form, the window does not re-size tot he form, but remains the current applcation window size.
So, without ANY specials code, you can 100% hide the access background window.
And if you re-size the access application window, then the form will re-size to fill out the current form.
This might look quite bad in some cases - such as this:
Now for above, I on purpose made the form background green - just to PROVE and show that that Access background window NEVER will display with above options.
So, the main issue here?
You can 100% hide the access background window. And you can now do this WITHOUT specials code. Just a few settings.
On startup, you can hide the ribbon - or build a custom one - again your choice.
But, your forms MUST NOT be popup forms anymore.
So, hiding the access background window is very easy - it then becomes a question of form size - size forms re-size to application window size - not the other way around.
On the other hand, if you adopt a tabbed interface (accross the top or left side), then your main window is always in display, and you are in effect swapping out the form (a sub form) for display of that given form. You can write your own code, or use a new navigation form - which does this for you).
If you need to launch separate windows, then you could launch them as popup from this main form - but that main form will of course always hide the access background if you follow above.
If you wish to hide the ribbon, then on your main form - load event, you can add this code:
DoCmd.ShowToolbar "Ribbon", acToolbarNo
So, your main form (which hides access background) could be tabbed inteface (SPA) or it could be a launcher form, and each option clicked on could launch a form as popup - which can be dragged anywhere on your computer - including to the 2nd monitor if you wish.
So, either forms stay always in the main applcation window - but never see the background. Or you use above, and launch forms as popup.

How I do Close Finddialog in fastcoloredtextbox

I can open Find dialog in fCTB by pressing ctrl+d but when I minimize my form and open another application, the dialog stay open and is on top (On other forms and applications)
I want to hide the dialog on leave the form or on click on FCTB.
How do I hide find dialog in fastcoloredtextbox?

How to maintain text in popup control even if click outside popup control

In my windows phone application I add one popup control for user login.
If user enter his credentials and click outside popup control then the data vanishes.
how to maintain data in popup even if user clicked outside popup?
Is there any property so that we can make background page ideal when popup window comes?
use IsolatedStorage for that to maintain data.
see the link
http://www.kunal-chowdhury.com/2011/06/windows-phone-7-mango-tutorial-12-using.html
hope this will help you...

Modifications to VB.NET PDF Viewer

Okay, I know a question LIKE this has been asked before, but none of them covered this certain toolbar. After the top and left toolbars are hidden, this little black window shows up near the bottom of the screen which allows the user to print, save, zoom, etc. They can also even open the top and left toolbars back up by clicking the Adobe logo.
As you can see, at the top of my program I have a toolbar of my own. The way my program works is a user will input data, press the 'Create Report' button and this Report Viewer window will popup. When the user Creates a Report a .PDF file named preview.pdf is created and that's what the user opens up. If the user doesn't like the report he can hit the X to delete it, or if he likes it he can type a File Name and Press Save. Or he can skip the saving and just print it. When the user saves the file it goes to a place that the software can retrieve at a later time. If the user presses the save button on one of the Adobe toolbars he has the option to save it where they want to. I can't have that.
Does anybody know how to disable ALL Adobe toolbars in the .NET PDF Viewer? (And yes, I know that Pressing F8 will bring them back up).
Here's the code I have now:
pdf.src = "C:\Users\Ryan\Desktop\HelloWorld.pdf"
pdf.setShowToolbar(False)
pdf.setView("fitH")
pdf.setLayoutMode("SinglePage")
pdf.setShowScrollbars(False)
pdf.setZoom(68)
Here's a screenshot of the Windows Form:
Acrobat viewer has such switchable options.
this configuration switchs off all navigation:
view=FitH
scrollbar = 0
toolbar= 0
statusbar= 0
messages= 0
navpanes= 0

Application hangs on clicking "Choose" button in IKPictureTaker view

I am facing a strange hang issue with IKPictureTaker and on clicking a "Choose" button. I am doing below operation using IKPictureTaker.
When a user wants to change a profile picture, upon clicking "Change Image" button, I display a IKPictureTaker view along with "Choose" button by setting IKPictureTakerAllowsFileChoosingKey to YES.
First time on clicking the "Choose" button, open panel will be displayed allowing user to select an image of his choice.
Next, on clicking the "Set" button, internally I am calling a profile picture upload function of a server in a separate thread and everything works great.
Next if the user tries to do the operation 1) and 2) again application hangs on clicking the "Choose" button.
After investigation I found that this issue is something to do with the background upload operation I am doing with the server.Because if I comment the upload part of code everything looks good.
I don't see any issues with the upload operation performed in the separate thread and it gives up it s runloop once it is done with its upload operation and all UI related operations again taken care in the main thread.
Application hangs only if I click on the "Choose" button. If I select the recent pictures or take a new photo using the camera everything works great.
Is there anyone who faced the same issue? Is it something to do with the NSOpenPanel displayed when we click on the "Choose" button?