Killing locks and sessions in access

[decklyn]

Hello,

I'm an Oracle developer - not an access developer - but my team has recently been designated support for an old access database that the business built... I know I know an IT nightmare right?

Anyway, we frequently get locks in the database which are not resolved by logging off all of the local users on the box (box is server with WTS). The lock must be originating from a network user.

I've had similar problems in oracle and wrote scripts that query the V$ tables to identify which sessions are holding the lock, where they are located, by which user, and then the session and serial ID are available which can be used to kill the sessions that hold locks.

Is there an equivalant in access?

 

[boblarson]

Well, the first thing to check is that each user has the rights for deletion on the server location where the database resides. If the last person out does not have those rights then Access can't do its clean up work and delete the ldb (locking) file.

 

[decklyn]

Well, the first thing to check is that each user has the rights for deletion on the server location where the database resides. If the last person out does not have those rights then Access can't do its clean up work and delete the ldb (locking) file.

I'll check that out once we get access.
I'll try to do some more access on how the locking works in access.
If I remove the ldb file will it release any locks on the database?
Thanks!

 

[boblarson]

I'll check that out once we get access.
I'll try to do some more access on how the locking works in access.
If I remove the ldb file will it release any locks on the database?
Thanks!

It all depends on what "locks" we're talking about. If someone made a change to any of the forms, or the database, which implemented record locking (not recommended that is done) then that can affect things as well.

 

[pkstormy]

To avoid locks with multiple users in the same frontend mdb/mde, you can use this script here which works very well and will prevent (*.ldb locks). You can have 100's of users.

http://www.dbforums.com/6274786-post19.html

I guarantee you'll never have to search down users again to see who has the mdb opened and has locked the *.ldb (and then have them all close out so you can compact/repair the mdb to repair the *.ldb file and then let users back in!)

 

[ghudson]

To avoid locks with multiple users in the same frontend mdb/mde, you can use this script here which works very well and will prevent (*.ldb locks). You can have 100's of users.

http://www.dbforums.com/6274786-post19.html

I guarantee you'll never have to search down users again to see who has the mdb opened and has locked the *.ldb (and then have them all close out so you can compact/repair the mdb to repair the *.ldb file and then let users back in!)

Interesting.