By "won't release", do you mean that the .LDB file is not being automatically deleted when
the last user exits the database? If this is so, then with everyone out of the database,
try deleting the .LDB file. Note that all users must have RWCD privilege on the folder.
An easy test for this is to have each user perform the following sequence of operations:
1.) save a new text file to the file share using Notepad
2.) re-open the text file, make an edit, save and close the file and
3.) delete the text file.
I have encountered situations where network administrators in the company I work for tell
me that they have set the folder privileges correctly, yet this simple test fails for one
or more of my users.
If you find that the .LDB file still persists, after the last user exits, then you may
have some corruption going on. Sounds like now would be a good time to import all of the
tables into a new database. You aren't attempting to share the entire database are you?
Hopefully, you have it split into a front-end (static tables, queries, forms, reports,
macros and modules) and a back-end (shared tables) databases. If not, you should do this
now.
From: Introduction to .ldb Files
http://support.microsoft.com/?id=208778
"Whenever the last user closes a shared database, the .ldb file is deleted. The only
exceptions are when a user does not have delete rights or when the database is marked as
corrupted; then, the .ldb file is not deleted because it contains information about who
was using the database at the time the database was marked as corrupted."
Tom
_____________________________________
I have an ldb file that won't release, it always says
that its locked by person trying to make changes.
It always changes to what ever computer you are using.
I have seen this before, but usually it will release on
its on.
Thanks
