On ldb files and lost changes.

[Spudhead]

Only vaguely related to ASP I'm afraid - not sure where else to put it.

We're having problems with an Access database losing data.

It runs a site that gets a fair few hits, but shouldn't really trouble it.

There is ALWAYS an .lbd file for the database. This should not be.

I'm as certain as I can be that not one connection is opened without being duly closed.

The site runs fine; we can add, edit and delete records. Sometimes, however, these changes will be reverted. Maybe the
next day, maybe a week later.

I'm also as certain as I can be that no other process (it's a large corporate network) is accessing or altering the database file.

We've rebuilt the database, with a new filename and a new DSN pointing at it. No change. As soon as the database is accessed, an .ldb file is created and it doesn't go away.

What could be causing:
a) The database to lose data
b) The .ldb file to not be automatically deleted

(and yes, I know (b) could cause (a) :))

Any ideas?

[scroots]

i think an lbd file means the database is locked ie somebody is altering it.

scroots

[Spudhead]

Yeah, but the only thing that should be altering the database is the website, and that shouldn't leave it locked. It should open, change and close in as long as it takes to run through the code; unless I'm opening a connection and forgetting to close it, which I'm sure I'm not. That ldb file should not remain on the server.

[Roy Sinclair]

Open the ldb file with notepad and see who it's pointing to. Usually the user id or machine id will be in that file.