Colin:
Still trying to figure out the correct form properties. The are the ones I currently have for three forms:
Code:
Form Change Property To Original Property Value
==== ================== =======================
F121_N1S_StaffmemberList No, No No, No
F122_N1S_Staffmember No, No Yes, No
F105_N1S_LogoutStatus Yes, No Yes, Yes
Now, having changed the properties as shown above DOES make form F105_N1S_LogoutStatus pop up in front of F122_N1S_Staffmember (in version 3 -- attached in most recent post).
HOWEVER, at this time, the "Ok" and "Quit" buttons cannot be clicked. That is, a user first had to realize the the form F122_N1S_Staffmember (it is visible while it sits behind F105_N1S_LogoutStatus) needs to be closed first.
This is a major assumption and, arguably, the majority of users may not realize that. So, ultimately, their only option is to way out the time. Nevertheless, this is confusing (i.e., the warning tells them they have up to 5 min to finish the work) and potentially frustrating for the user.
I tried the variations of the acDialog such as:
DoCmd.OpenForm "F105_N1S_LogoutStatus", , , , , acDialog
DoCmd.OpenForm "F105_N1S_LogoutStatus", WindowMode:=acDialog
In this case, F105_N1S_LogoutStatus pops up but disappears automatically with ~ 1 second. That's not enough time to read the warning message.
So, no matter what I've tried, the shutdown process itself works but the status message is either not visible on top of **all** forms or it shuts down too quickly (acDialog... I don't even know if the Ok/Quit command buttons would work w/ the acDialog).
Sorry to keep on bothering you, Colin... however, you're the #1 SME on this process.
Thank you,
Tom