Database Maintenance and Kick Users

[vanzie]

Does anyone have a sample database where the admin can kick current users out while doing maintenance? or to notify the users that database maintenance is scheduled and have them locked out from using the database

 

[theDBguy]

Hi. Have a look here.

UtterAccess.com

www.utteraccess.com

 

[vanzie]

It is far better to do your maintenance during off-peak hours when possible but you will still need code like this if your users have a habit of going home without closing the app properly.

I've disabled the close button so the users are forced to log out first but they still leave the app open but the next users just continue on their account and I don't want that to happen

 

[CJ_London]

What maintenance are you referring to? forms/reports? data? table structures?

they still leave the app open but the next users just continue on their account

what does this mean? are users sharing the same machine?

 

[vanzie]

What maintenance are you referring to? forms/reports? data? table structures?

what does this mean? are users sharing the same machine?

No there are 3 different computers in that control room but they use the front end file on the network. So if user 1 uses PC 1 and goes off duty, user 2 comes in to use PC 1 with user 1's account still logged in

 

[vanzie]

No there are 3 different computers in that control room but they use the front end file on the network. So if user 1 uses PC 1 and goes off duty, user 2 comes in to use PC 1 with user 1's account still logged in

And if I should do maintenance, it will be to update a report or make small changes to some errors picked up. Maybe I found new code that I can implement in that app

 

[CJ_London]

better explain your setup - is the db split? and each machine has their own copy of the front end?

missed this comment

they use the front end file on the network

each machine must have their own copy of the front end - sharing a front end on a network is the way to corruption.

 

[vanzie]

better explain your setup - is the db split? and each machine has their own copy of the front end?

We use a network share drive. They log in on the same front end file but don't have access to the back end file.

 

[CJ_London]

the back end file is Access? or SQL server/something else?

I presume the network share is not terminal server or citrix? If not, you are seriously risking corruption - each machine needs it's own copy of the front end on it's local drive and needs to be hard wired to the server (unless using terminal server/citrix in which case the front end will be on the server, but again a copy for each machine in their respective profile directories)

Either way, by ensuring each machine has their own front end copy, you can work on a master copy and update a table in the back end to indicate there are updates available. The front end interrogates the table on a regular basis - might be a form timer, might be an event that happens regularly such as opening a form - and if it picks up there is an update, closes, copies the new front end to the local drive and reopens. Plenty of examples out there how to do this

 

[vanzie]

Thank you for your inputs, gents. I'm not as advanced in databases as you guys but I did read about splitting databases and put some of that info into practice but i'll work on a better one next time