URGENT!!! Security problem

The system.ldb shows that there is users connected. But, I closed all there applications and even there computers, and the ldb still shows the list.
When we try to reconnect to the DB, it says that there is someone still connected in exclusivity. ALL the computers are OFF!!!
We can connect thru «shift» but I don't want to give this key to the users.
What can I do?
There is 20 users waiting for a connection.
Please help me!
Any solution (even a "maybe...") is welcome.
Newman

1) Get everybody out
2) Delete the .LDB
3) Let em back in

RichM

It will work for now but it isn't always a good idea to delete the .ldb as at somewhat it could prevent you from getting into your mdb. Make sure that directory also has delete rights but filter the delete rights on the actual MDB. This should hopefully fix the problem. If not it would be better to check the files that are in use in your file server and release it. Sometimes the NOS will think it is still in use.

NShafranski:
It will work for now but it isn't always a good idea to delete the .ldb as at somewhat it could prevent you from getting into your mdb.

Click to expand...

How can deleting the .ldb file prevent a user from opening the database? The .ldb is only used for tracking record locks and user ID's. The .ldb file will delete itself when the db is properly closed and all users are out of the db. The .ldb file can not be deleted if the database is opened and/or if the db thinks somebody is still in it but the db was not properly shut down like when a user hits Ctrl + Alt + Del and chooses End Task on the db. Sometimes when that happens, all users who were in the db have to reboot their PC's to cut the link to the db.

FYI: You can open the .ldb file in notepad.exe to view who is in the db or was in the db while it is still open by at least one user. It will show their workgroup name and computer name.

I was not able to delete the ldb file, but was able to erase it's content. But nothing changes.

I reconnected every computers and disconnected them again, and it worked fine.

Thank you ghudson for your post, but it was a little bit too late.

The problem is that someone closed the computer with the power switch instead of using the close option of the Start menu, while Access and other applications were still open.

Users!!!
Thank you anyway!
Newman

I've seen some code posted that will shutdown Access during a power shutdown to eliminate this problem but I don't remember quite where I saw it. Do some searches and mayber you'll come up with something. I've had the same problem of delete the ldb and have found that (in my case of a split database) that if I open Access, File-Open the security file, the system will promt for repair and generally resolve the lockout. With a secured database I have also found that if someone shuts the database down and immediately tries to get back in (like within 1 or 2 seconds) that this will cause a lockup because the ldb file hasn't finished getting rid of the user before they try to get back in.

Autoeng

Yes Mr ghudson, I'm full aware what the purpose of the .ldb file. I've seen rare instances when users could not get back into the data only admins after the .ldb file was deleted. Now he cannot delete the LDB file even when the users have rebooted leads me to believe that they do not have delete rights to this directory.
Newman - check you NOS to see if the LDB and the MDB are in use by the server. You can purge these two files and then delete the ldb and they should be able to get back in.