Code to disconnect users while update is running

[Glenn_Suggs]

Hello everyone. This will probably sound like an unusual request, but I have been asked to disconnect users that have left their PCs logged on and running a certain Access application. The application has a nightly update routine so as to not conflict with other stuff running on the system, but sometimes users leave the network-based app running on their machines and this results in the update not running to completion. Does anyone know of a way that the app can programmatically detect this situation, possible using the .laccdb file and the "Machine name" information it contains to accomplish this task? I'm thinking it's going to be tricky because some of the info in the laccdb file seems unique while others (four of them today), only say "Admin".
Thanks in advance... Glenn

[ItsMe]

You could have a table of users on the BE that indicated who was logged in. In that table you could have an additional Boolean field that would indicate if a given user is in the middle of a process that requires completion before logging off. In my DB's I often have processes, that once started, are required to be completed before the user closes the form and or closes the DB.

Another approach would be to look for the lccdb file on the client machines before closing that FE file DB.

What I do is use script on a non-related machine to do a backup of the BE file regardless of who is still logged in. I have another script that looks for the lccdb file on the server. If the lccdb file does not exist on the server, I then run script to do a compact and repair on the BE file.

[Glenn_Suggs]

You could have a table of users on the BE that indicated who was logged in. In that table you could have an additional Boolean field that would indicate if a given user is in the middle of a process that requires completion before logging off. In my DB's I often have processes, that once started, are required to be completed before the user closes the form and or closes the DB.

Another approach would be to look for the lccdb file on the client machines before closing that FE file DB.

What I do is use script on a non-related machine to do a backup of the BE file regardless of who is still logged in. I have another script that looks for the lccdb file on the server. If the lccdb file does not exist on the server, I then run script to do a compact and repair on the BE file.

Thanks for the response. You have some good ideas here I think. I will try implementing part or a combination of them. They make a lot of sense. Thanks again.