Unlock mdb file and/or log off user 1

[jlitondo]

Is there a way to unlock an mdb file that has been locked by a user on a machine. I have a database that is still locked by a user on a machine even after they've quit the application. I tried rebooting the pc to no avail.

 

[DanJR]

ummm, I'm no expert in this area...

Which version of Access are you using (Access 97?).
Does the user open the Db in 'Exclusive mode'?
Is the Application split into a front end and back end?

Cheers,
Dan

 

[jlitondo]

Actually this application is not split for now since we just started running it on a new wireless network and we can't afford to have it down for long (over 30 mins etc)if the network goes down and I only have 3 users on it at a time....
Its written in Access 2k. The database is set to open in shared mode but even after all the users are logged off, one user-machine still clings to the ldb file, hence locking the db.

 

[pweegar]

Sounds like the application left the ldb file open. Can you delete the file then do a compact and repair on the db. Try killing the open file from the server.

 

[jlitondo]

Rebooting the client pc unlocks the mdb so I'm able to delete the ldb file. But then after re-openning the mdb and compacting and repairing, the ldb is still open and undeletable. Whatever procedure access uses to delete the ldb file when users quit the app isn't running right against this mdb.It would be nice to be able to programmatically force all users out of the app without rebooting the pc. Anyone know how to do this?

 

[mok44]

HI
Not an answer but a related problem: I am running an Access XP database with a BE on a server and FE on 6 stations. Occasionally users get locked with "Unrecognized database format" error, which seems to point to the BE, as the FE is still functioning. Then I have to kick everyone out and compact and repair before users can get back in. Any thoughts? Thanks for your help.

 

[bartsimpson]

Microsoft have a little known utility that tells you who's logged in to the database, and who has corrupted it. Click here to get to the MS KB article :

http://support.microsoft.com/default.aspx?scid=kb;EN-US;176670

MS databases do tend to corrupt in a multi user environment on NT servers. You need to disable opportunistic locking.
See the MS KB article :

http://support.microsoft.com/default.aspx?scid=kb;en-us;129202

In general, you need to disable Opp Locking. Do this on NT by setting the registry key to 0.

 

[jlitondo]

Thanks bartsimpson, the tool works great!

 

[JaCu]

I’ve had a similar problem with lingering .ldb files on A2000 shared databases. It seems that the lingering file only causes Access to ‘think’ a database is open when in fact it may not be. When you’re sure everyone has logged out, you can change the .ldb extension then delete the file. I just add ‘1’ to the end and make it ‘databasename.ldb1’.

Not sure why this works but give it a try in a pinch.

Hope this helps.

 

[bartsimpson]

It sounds as if your problem is with the .ldb file holding a user connection open. Use the tool that I mentioned above to kill the connection, and all should be well.