Need to gain exclusive access to a multi-user database

[alan2013]

I administer a MS Access 2010 database in a multi-user work environment, and pretty-much always have difficulty in gaining exclusive access in order to implement changes. Sometimes, it's because some people lock and spend time away from their PC while still logged into the database, and sometimes people aren't aware - despite my efforts - that I need everyone to log out. There's no way of killing these sessions....and in any case that might have pretty dire consequences. Can anyone think of a good solution to this, please ? Thanks, Al

 

[Catalina]

Are you referring to making changes in the back-end?

 

[pr2-eugin]

There should be several examples on the Internet to "Detect User Idle time or Inactivity".. Check them out.. They might be the key for this..

 

[alan2013]

Not as such. The idea is that, once I've implemented changes to a 'development' version of the db, I need users to come out of the live version. Once they have, I switch the files round, basically. Once switched, users can access the new db.

 

[Catalina]

But your application is split in front- and back-end?

 

[missinglinq]

Have never needed it, but here's some code I found a while ago to do just that:

KickEmOff

Sadly, the author of this code is that person familiar to one and all, 'Anon!'

Linq ;0)>

 

[boblarson]

But your application is split in front- and back-end?

As Catalina asks, is it split with backed (tables only) and frontend (the rest)? And, if not it needs to be. If it is, each user should have their own copy of the frontend on their machine and should not be opening the same file on the server. Then, when you do your updates you can just release a new copy of the frontend. You can do the updates on peoples' machines with many methods. I have a free tool on my website which lets you enable auto updating so if you do a new version, the person opens their copy and it tells them it is out of date, closes, copies the new file to their computer, and reopens for them.

 

[jdraw]

Not as such. The idea is that, once I've implemented changes to a 'development' version of the db, I need users to come out of the live version. Once they have, I switch the files round, basically. Once switched, users can access the new db.

Please tell us exactly what you mean by

a 'development' version of the db

. Are you talking of the FE or BE?

 

[alan2013]

Thanks for your contributions. I've tried out 'On Timer' and 'Timer Interval' under 'Event' for the 'Main menu' Form, and I think that'll suffice, for now at least. Thanks again.