ldb file lock no one in db

[Jgk]

I have a db that's opened in remote web apps and periodically a ldb lock file is created even though no one is db. I have IT shut down server and ldb still there. I can delete file and then everything works fine, but want to know what computer created this file and left db in this state. What would you recommend to diagnose this problem.

[ItsMe]

Sounds like your remote user is experiencing a runtime exception or is loosing their connection to the BE file while executing.

[Jgk]

Yes, but how do I tell who lost connection. What is the procedure. Is it ok to delete ldb after ensuring no is in db?

[ItsMe]

When I have an orphan laccdb, I delete it. However, I do not usually see them in production DB's. If I do see them in a production DB it is usually predicated by a phone call from a user that experienced a problem. Like you said, you first ensure nobody is connected and then delete the laccdb.

I create orphan laccdb files all the time when debugging. I expect that to happen sometimes as I beat up my apps. Since you have a remote connection, I would start with that and that requires help from network engineers/maintenance.

[Jgk]

How do you read ldb file I tried open with notepad but no luck.

[ItsMe]

How do you read ldb file I tried open with notepad but no luck.

Never tried it. I suppose it would have some tell tale info in it. Perhaps you can glean some info from the DB's system tables. Are you using an MDB format as a back end?

[Jgk]

Yes it is split db

[ranman256]

If you need in the mdb, just delete the ldb. If its active/in use, it wont delete.
If its an orphan, it will go.

[ItsMe]

That's a good point. It should not be able to be deleted when the system depends on it.

As for how to solve the problem and not the symptom, I do not know.