Setting as popup allows form to sit above the application window. Without popup form can be moved but it will be within the window. Do some experimenting. Keep in mind that popup and modal can be a bit annoying when developing and debugging database. Suggest not setting until ready to distribute to users.
Setting as popup allows form to sit above the application window. Without popup form can be moved but it will be within the window. Do some experimenting. Keep in mind that popup and modal can be a bit annoying when developing and debugging database. Suggest not setting until ready to distribute to users.
Correction:
Unlike popup forms, modal forms are part of the application interface. They do not appear above other interface objects unless they are also popups
@moi
There is also a third option acDialog which is only available in code
DoCmd.OpenForm "YourFormName", , , , , acDialog
When this is used, it prevents all other code running until the form is closed
You obviously can't click on the other form as its modal. That means it remains the active form.
Whilst its the active form it appears at the top of the z-order.
However it is part of the application interface and doesn't have the same properties as a popup.
Drag it to the left and it goes under the nav pane. Ditto if moved up to the ribbon.
Popups move over the NP or ribbon etc
Correction:
Unlike popup forms, modal forms are part of the application interface. They do not appear above other interface objects unless they are also popups
My db is set for Overlapping Windows, not Tabbed Documents. Popup Yes would be required for form to open over other objects for Tabbed Documents. For Overlapping Windows, even Modal alone opens over other objects.
I use Overlapping Windows. I was trying to clarify the difference between modal (part of the application interface) and popup (separate from it)
Try opening a popup form followed by a modal form.