Possible Causes for .ldb File

[Steve Murphy]

I'm doing some maintenance on an old project that uses VB6 as a front-end to
Access97. When the application closes it leaves behind an .ldb file with a
few locked tables in the database.

So far, I've been tracking the problem by ensuring all queries, tables, and
dynasets, as well as the database itself, are closed when no longer needed.
But the .ldb file and locking persist. Any suggestions? Should I be looking
for anything else?

 

[Dirk Goldgar]

I'm doing some maintenance on an old project that uses VB6 as a
front-end to Access97. When the application closes it leaves behind
an .ldb file with a few locked tables in the database.

So far, I've been tracking the problem by ensuring all queries,
tables, and dynasets, as well as the database itself, are closed when
no longer needed. But the .ldb file and locking persist. Any
suggestions? Should I be looking for anything else?

Does you have delete permissions on the folder where the database is
stored (and the .ldb file is created)?

 

[Steve Murphy]

Does you have delete permissions on the folder where the database is

stored (and the .ldb file is created)?

Yes.

 

[Dirk Goldgar]

Yes.

Yet the application is closed. Hmm. Does this VB application create an
instance of the Microsoft Access application, or does it just use DAO to
manipulate the .mdb file? Have you looked in Task Manager to see if
there's any process running that could be holding the database open?

 

[Steve Murphy]

Yet the application is closed. Hmm. Does this VB application create an
instance of the Microsoft Access application, or does it just use DAO to
manipulate the .mdb file? Have you looked in Task Manager to see if
there's any process running that could be holding the database open?

Interesting. It appears that the VB application was staying alive in the
background. I added an "End" call to the startup form's Unload event and the
problem seems to have gone away--although I'm not sure why that is
necessary.

For the record, the application just uses DAO to access the .mdb file.

Thanks.

 

[Dirk Goldgar]

Interesting. It appears that the VB application was staying alive in
the background. I added an "End" call to the startup form's Unload
event and the problem seems to have gone away--although I'm not sure
why that is necessary.

Dunno. It sounds like there's some object reference that is still
alive.