.ldb file

[Guest]

Hi All,
I have a few databases. I created a test database from my existing live
database because I need to make a few design changes. The fe resides on my
home directory and the be on the network. After I perfected the design and
created forms, I created a new database to copy those items into. Both the
FE and BE of the new database are on the network.

I currently have a .ldb file on the FE and BE of the new database, as well
as the Test database. I delete the .ldb but it comes back, in some cases, it
won't allow me to delete. I have reviewed other threads on this subject but
could not determine the problem.

I have Admin rights
There is no security on the database to be concerned about.
There should not be any other users but I cannot determine that with
certainty except for the copy that is on my home directory.
The .ldb owner is myself.
I have checked to make sure the database isn't minimized on my desktop.

Is there anything else?

Thank you
Capt OhNo

 

[Guest]

..ldb files control locking of your database. Every time you open the
database, an .ldb file will be created. It will also be deleted when you
close the databaes. Sometimes if there is an error that causes the database
to close abnormally or, for example, you close it using the Task Manager, the
..ldb file will be left behind. Only then should you delete the .ldb file.

 

[Guest]

Klatuu,
You have told me what you know about .ldb files but it really doesn't answer
my question. Why does the database keep generating the .ldb files? The only
thing that I read on the email threads that I am unable to determine i s
'Access thinks something is open'. I don't know how to troubleshoot that.
The .ldb files keep generating after I delete them.
Capt OhNO

 

[Guest]

Reread the first sentence of my original post. Every time you open an .mdb
file, an .ldb file is created. It happens automatically. It is a file that
Access uses to control locking. How much more clear can I make it?

What is your concern with the .ldb file, anyway? As I said previously, when
Access closes normally, it deletes the .lbd. It is possilbe for one to be
left haning if Access is terminated abnormally.

You can't delete an .ldb file while the corresponding .mdb file is open.
There is no reason to do so.

I still don't understand what the problem is.

 

[Guest]

Klatuu,
I wasn't trying to delete the file when the database was open. It was
closed but the file didn't delete automatically as it is supposed to - an
indication of a corrupt database. How much more clear can I make it?
Captain OhNo

 

[Gina Whipp]

Hmmmm, okay a few questions:

Windows version and Access version?
Is your version updated, latest version of Jet, etc...
Any coding in the OnClose of say a Main Menu form?
How do you (or anyone else) close the database?
When was the last time you ran Compact & Repair?

Because an .ldb hanging around is sign of corruption, you want to eliminate
the obvious before jumping the gun...

 

[Guest]

Now you made yourself clear. I have seen this happen once. I can't remember
how we fixed it. I can't find the other gut that was involved, but as soon
as I can, I'll get back to you with a procedure that will fix it.

 

[Guest]

Okay, Captain, here is what I found out. I don't know if this was an issue
for you, but our problem was multiple users with the same .mdb file open.
What we had to do was force all users who had it open to close it. Then we
were able to delete the .ldb.

If you are the only one with it open, I don't know what would help. If it
crashed, it might help to look in Task Manager and see if Access is open
either as an Application or a Process and end it if it is.

I hope this helps.

 

[Guest]

Klatuu,
I wasn't trying to delete the file when the database was open. It was
closed but the file didn't delete automatically as it is supposed to - an
indication of a corrupt database. How much more clear can I make it?
Captain OhNo

Hi,

I've come across the same situation at my work where an LDB file for a
database is still there after the MDB file has been closed, and there are no
other users opening the MDB file. Deleting the LDB file does not work as it
always reappears.

In my experience, what works is not opening the MDB file for a couple of
hours, and the LDB file automatically goes away. In such instances, I've
found that my database was not corrupted - just not closed properly. So, an
LDB file w/o MDB file may not always mean a corrupted database.

I don't know why this happens, but possibly, the Operating System realizes
that the LDB file shouldn't be there (because there is no open MDB file for
it) and deletes it after a certain period of time. Using Windows XP/Access 2K
here.

HTH,

-Amit

 

[Guest]

To All:
Thanks for your help and response.
It is acs2000 and have been using it with my current windows version for two
years.
I think Amit's response solved it. Ignore it and it will go away.
I once again deleted the .ldb files and compacted the database again. It
may be just an anomaly but seems to have stopped occuring today while it was
persistant yesterday using the same techniques to solve.
Perhaps there were hardware issues, as some threads suggested. I compact
before I backup each week so it wasn't my first time. I continued reading
through previous threads and Microsft Knowledge Base and decided that if it
is corrupted it is very technical to repair. Since this was not a live
database yet, I was going to create a new one and copy everything to that
one as one thread suggested. I just didn't understand why it kept happening.
The good thing though, is that it was under development and not my live
database.
Thanks especially to Klatuu.
Captain OhNo