Dirty Exit

  • Thread starter Thread starter F1stman
  • Start date Start date
F

F1stman

Hey Folks,

I am having trouble with my DB closing and leaving the .ldb file open. The
users then cannot open the DB until the .ldb has been deleted manually and
the information must be re-entered. What script or macro must I use to make
sure this doesn't happen? I know it has something to do with the OnDirty
event.

Many thanks in advance.

Adam Kemp
 
Hey Folks,

I am having trouble with my DB closing and leaving the .ldb file open. The
users then cannot open the DB until the .ldb has been deleted manually and
the information must be re-entered. What script or macro must I use to make
sure this doesn't happen? I know it has something to do with the OnDirty
event.

Many thanks in advance.

Adam Kemp
Click to expand...

Ummm... no. It doesn't.

The .ldb file is created when you first open the database, updated with the
new user's ID when a second user opens the database, and should be deleted
when the last user exits the database. It has nothing to do with Forms or
Tables or the On Dirty event (which fires when any entry is made to a bound
control on a form) - just who's got the database open.

If you're crashing out of the database, or powering down the PC, or rebooting
while the database is open the .ldb file will be left hanging. It's also VERY
likely that the database itself will be corrupted perhaps irreversibly. If the
database is closing on its own for no apparent reason, You Have A Major
Problem that needs to be addressed!

If you're exiting normally from the database and the .ldb file is still
hanging around, make sure that you (and all the users who use the database)
have full Read, Write, Create and Delete Windows privileges to the folder
containing the .mdb file.


John W. Vinson [MVP]
 
Back
Top