If it were me, I think I would approach it using the onTimer event as well.
What you could do is this: If all user's see the same server drive letter,
such as F:, you could create a kill file that, when placed on F:, would
cause other user's programs to exit out. So say you want to remotely boot
everyone from the program, and you know it is safe to do so (that a user
just left his program running, even though everyone's gone) create a file
called, exitdb.txt, and it wouldn't matter what was in the file.
Now, on your program file's mainmenu form, you could do an OnTimer that
maybe checks for the existance of this file every 5 minutes or so. If the
file is found, it then does a docmd.quit (preceeded by a save all).
So when you want to initiate the remote shut-downs, you could copy this
exitdb.txt file to your f:\ drive, or other shared folder on that drive.
Wait 5 minutes, and all should be well.
Of course, if users' have their pc's set to hybernate, it wouldn't work.
Just a thought...
"ManningFan " <ma********@gma il.comwrote in message
news:11******** **************@ p77g2000hsh.goo glegroups.com.. .
If one of my end users has left their database open and I need to
compact it, is there a way (via code or something else) to boot a user
from a database and clear the LDB file?
I'm pretty sure short of an OnTimer event to quit the database that it
can't be done, but maybe someone out there has done something like
this. I kno wyou can break the connection via user access through a
server but the solution must be Access based for it to be useful to me.
