Occasionally, after sending data to our database, the .ldb file remains open.
I know this can be caused by not shutting down the database properly.

Is there a way to programmatically close the .ldb file? Thanks......
--
JT

This per Gunny, found at Microsoft.mailarchive.ca

"The file is locked by some other process than the one you tried to kill.
Perhaps this is a multiuser database being shared on the network? (This is
a no-no, but I know people do it all the time.) If so, perhaps one of the
other users is connected to the MDB file. If so, have that user quit the
database application. Use the LDB Viewer to see which workstations on the
network are currently connected to the database.

If that doesn't work, ask the Windows Network Admin to remove the file lock.

If this database application isn't networked, then look to see what other
process is connected to the MDB file, such as an Excel spreadsheet, and when
you find it, save your work and close that application to remove the file
lock. If you can't find the process that is locking the database, then save
all your work and reboot the PC where the database is located. That will
remove the file lock."

Alan



"JT" wrote:

Occasionally, after sending data to our database, the .ldb file remains open.
I know this can be caused by not shutting down the database properly.

Is there a way to programmatically close the .ldb file? Thanks......
--
JT