Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

here is my situation:

i am wondering if there is a permissions solution. perhaps i can have the network guy remove the ability for anyone to edit except for me?

do you know if there might be disastrous impact on the database itself if i go this route?

i have a bunch of users connecting to the backend of an access database, i need to edit the back end but unfortunately cannot log people out.

share|improve this question
Have you considered just adding some logic into the front-end to log access of the database into the database when a user open/closes it? If you know who is causing the problem you could fall back to publicly ridiculing them. – Zoredache Oct 18 '10 at 23:40
There is no server-based/permissions solution to this. You can't change the permissions on a file while it is open, and if you change the permissions to prevent your users from entering it, they won't be able to edit their data. The solutions cited in the answers on SO are your only solution. Of course, I've been doing Access apps with Jet/ACE back ends since 1996 and this has only been an issue in one application I've ever had running. In that case, I put in log-off code that shut down any running instance of the front end at midnight. – David W. Fenton Oct 19 '10 at 0:00
up vote 1 down vote accepted

I see I responded to that question. Why won't my response there, copied below, work for you? Alternatively you could have a hidden form with a timer set to go every, say 60 seconds, and check a field in a table in the backend to exit users out.

Idle Detect/Inactivity Timeout

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.