MS Access and Lock Files (*.ldb)

[vatik]

I have setup a set of asp scripts to handle database interactivity throught a local netword. All databases (created in ms access) are hosted on the server. I have several different applications for these scripts. The problem lies when using the scripts to access the database, throught the I_USR account. As expected a database_name.ldb file is created. The problem lies with it remaining open even after the websession has been terminated. When the file is opened it list the machine the user logged on from with the user Admin, regardless of the current user. This indicates the user and machine that has locked the database. I have checked to see that all the connections and record sets have been properly closed. The file remains which is causing problems for the department wanting to edit the database via Access and not the scripts. I suspect the problem has something to do with exclusive locking permissions, but I have not been able to solve the problem as of yet. If anyone is able to assist or needs more details, it will be greatly appreciate and probably help my review this Friday *smirk*. Thank you for reading all this. - vatik

 

[Databaseguy]

Here's evrything I've learned about LBDs and locking. Some of it pertains directly to Access. You can apply this to ASP as applicable.

1. If you don't have delete rights where the database resides, the LDB file will remain after you exit the database. (I'm unsure what happens next. I think that if someone else can get in, and they have rights, the LDB is destroyed.) Users need full control to directories where DBs are stored

2. If you open a database where there are no users logged in, and you only have read rights to the directory, no LDB is created and you'll lock everyone else out until you exit. This happened even if the DB is set to Shared

3. If you have a front end-back end DB, no LDB is created on the back end. Only the front end has an LDB (Unless you don't have create rights, see 2)

4. Sometimes something gets a hold of the process. Server/thread/whatever (I'm not sure) and won't let go. The only workaround I've seen is to re-boot the server. (Ouch)

5. Access defaults to the last open method used when you use a shortcut or recent file menu. To get around this, open Access first, then use the file/open method. (As opposed to double clicking an Icon or using a history menu)

6. Be careful who makes design changes, because they may not be able to access the DB next time, copy .mdb files, or delete .ldb files

7. Improperly exiting a database can corrupt the LDB file

8. Improperly releasing objects may have an impact. However, during testing, I have not found this to be the case Tyrone Lumley
augerinn@gte.net

http://server47.hypermart.net/databaseguy