Access behaving badly. (2 Viewers)

[John Sh]

I am running Access 2016 on Windows 11 and am experiencing some odd behaviour over the last week or so.
Firstly some, not all, of my popup/modal forms are going behind the calling form.
To get them to sit on top I have to make them modal but not popup.
Secondly when I open some forms in accdb they close the navigation pane.
Also I have noticed some of my major forms, not popup or modal, have been changed to popup/modal.

Is W11 messing with my version of Access?

 

[DHookom]

Does this happen in all databases, on all computers?

 

[John Sh]

Does this happen in all databases, on all computers?

I only have one computer to try it on, so not knowing, cannot say.

 

[isladogs]

Can you upload a simple repro database that exhibits these problems?

 

[GPGeorge]

I am running Access 2016 on Windows 11 and am experiencing some odd behaviour over the last week or so.
Firstly some, not all, of my popup/modal forms are going behind the calling form.
To get them to sit on top I have to make them modal but not popup.
Secondly when I open some forms in accdb they close the navigation pane.
Also I have noticed some of my major forms, not popup or modal, have been changed to popup/modal.

Is W11 messing with my version of Access?

Clarifying questions.

Does this happen in all accdbs? Does it happen in only one accdb?

Who uses these databases, besides yourself?

 

[MajP]

to get them to sit on top I have to make them modal but not popup.

That is opposite of what you should be doing. Pop up brings it in front, and modal restricts leaving it.

A Popup form floats above all other Access windows.
What Popup does
The form becomes a top‑level window, not embedded inside the Access application window.
• It stays in front of other Access forms.
• You can still click other forms, tables, or the navigation pane unless the form is also modal.

A Modal form forces the user to deal with it before returning to anything else in Access.
What Modal does
• Prevents clicking other forms, tables, or the Access UI.
• Forces the user to close or complete the modal form first.
• Does not make the form float; it can still be inside the main Access window unless Popup is also set.

Modal + Popup = true dialog box behavior
When you set both:
• The form floats above everything (Popup)
• The user cannot interact with anything else until they close it (Modal)
• It behaves like a custom message box or dialog window

 

[John Sh]

I'll try to answer you all.
I have tried this on another computer and the popup behaviour is normal. I.e popup yes and modal yes, the form is on top and must be closed.
Colin. The forms in question are part of a large system. Separating the form is easy. Separating the underlying functionality is not so easy.
George. I only have the one database that is split for use by a number of people at the local university.
The problem does not happen with the accdb file at the uni.
Majp. That is my problem. I can only get the form to sit on top if I set modal to no.
Not sure if it's relevant but I am getting .mdb files generated in the development environment and at the uni running accde files.

I normally compact and repair on close., there seems to be mixed feelings on this.
I just did a compact and repair, not on close, and the problem seems to have corrected itself.

Watch this space.

Thank you all for your interest.
John

 

[The_Doc_Man]

Not sure if it's relevant but I am getting .mdb files generated in the development environment and at the uni running accde files.

The "generated" files are significant if you weren't creating them yourself as an intended function of the program. When Access creates a .MDB file unexpectedly, that is a form of error recovery. You need to open the generated file AND the original file because one of them will have a table with some kind of error message in it. It has been so long since I dealt with one of these that I can NEVER remember which file (original or new) has the error in it. But that generated file is indicative of an Access "ugly" shutdown. The question to ask is, when that file gets created, do the users thereof report a crash or crash/restart? (That's an inclusive OR, not an exclusive OR.)