P
Paul
I'm running Access 2003 in a multi-user environment, and I've been using the
Timer event in the Main Menu form that's always open to close down all open
front end mdb files at the end of the day in order to compact and repair the
back end mdb file. I do this by renaming the extension of a file on the
network drive from ".no" to ".yes". The code in the form's Timer event
checks to see if the file named "close_app.yes" exists, and if it does, it
closes down the user's front end application. So I can make sure all the
users will close down and unlock the back end, even if the neglect to turn
their computers off when they go home at the end of the day.
I've been doing this for several weeks, and it works great, except when a
user leaves a Message Box displayed, or, if a user has a system-generated
error message. I know I should be trapping all of those, and I'm still
working on that. But in the meantime, I find that I sometimes can't compact
and repair the back end database, or modify it, because sometimes a user
goes home with an open message box displayed on their front end database.
Is there any way to overcome this limitation, like getting VBA to close all
open message boxes without user intervention after a period of time, and
also closing any error messages as if the user clicked "End?"
Thanks in advance,
Paul
Timer event in the Main Menu form that's always open to close down all open
front end mdb files at the end of the day in order to compact and repair the
back end mdb file. I do this by renaming the extension of a file on the
network drive from ".no" to ".yes". The code in the form's Timer event
checks to see if the file named "close_app.yes" exists, and if it does, it
closes down the user's front end application. So I can make sure all the
users will close down and unlock the back end, even if the neglect to turn
their computers off when they go home at the end of the day.
I've been doing this for several weeks, and it works great, except when a
user leaves a Message Box displayed, or, if a user has a system-generated
error message. I know I should be trapping all of those, and I'm still
working on that. But in the meantime, I find that I sometimes can't compact
and repair the back end database, or modify it, because sometimes a user
goes home with an open message box displayed on their front end database.
Is there any way to overcome this limitation, like getting VBA to close all
open message boxes without user intervention after a period of time, and
also closing any error messages as if the user clicked "End?"
Thanks in advance,
Paul