Cannot delete .ldb file

[Guest]

I currently distribute access 2003 solutions across multiple (win 2003)
terminal servers using the Access runtime as a front-end for end users. I
administer the databases in the background using Office Access 2003 on a
separate machine. Occasionally .ldb files remain within the file where the
databases are located. I am then unable to delete these files for days on end
even though I know for a fact that they are not physically in use by another
user. (the "Error Deleting File or Folder" message appears, notifying me that
I cannot delete the file as it is in use by another user or program). I
assume the problem could lie on the file server and not the actual databases.
I also think that if a user's terminal session is automatically disconnected
via an administrative log-off program, then the files they may have had open
continually remain in use for an indefinite period of time.

Is there any way one can remove / delete these stagnant .ldb files and
exclusively open the databases without corrupting them or the data they
contain.

Please help !

 

[Dave]

you are trying to fix a symptom rather than addressing the basic problem.
access makes a poor shared database unless you are very careful about how
you use it. the ldb file is the record locking file that is used to try to
coordinate locking of records between processes. that you have them left
laying around is a symptom that you are not controlling the access to the
data in a way that is inherently safe, most likely you have mapped forms
directly to tables or queries so that each user is keeping an open
connection that can edit data in the database. it is much safer to use
read-only access as much as possible and only allow editing of single
records and then only by wrapping it in a transaction so the whole update is
done at once in a safe way.

of course the 'right' way to do it is to go to a real multi user database
server like sql server.

 

[Van T. Dinh]

It is possible that the W2203 file management still think that the file is
open and therefore you cannot delete this. The server admin should be able
to close / unload it and then you can delete it. You can safely delete the
LDB file if the MDB/MDE is not being used.

However, to use Access database on T.S. with much reduced chance of
corruptions / locking, you should:

* Split the database application to Front-End and Back-End (done if I read
your post correctly.

* Each user should have a _separate_ copy of the Front-End, even on the T.S.

Tony Toews has the utility "AutoFE" that can help in this regard. See:

http://www.granite.ab.ca/access/autoFE.htm

 

[Tony Toews]

you are trying to fix a symptom rather than addressing the basic problem.
access makes a poor shared database unless you are very careful about how
you use it. the ldb file is the record locking file that is used to try to
coordinate locking of records between processes. that you have them left
laying around is a symptom that you are not controlling the access to the
data in a way that is inherently safe, most likely you have mapped forms
directly to tables or queries so that each user is keeping an open
connection that can edit data in the database. it is much safer to use
read-only access as much as possible and only allow editing of single
records and then only by wrapping it in a transaction so the whole update is
done at once in a safe way.

of course the 'right' way to do it is to go to a real multi user database
server like sql server.

Hmm, guess I'm doing something wrong then. I use bound forms all the
time. One of my databases has 25 users in all day all the time.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm