<div>
It can be. &nbsp;It depends on if the user/process has delete rights on the file and directory.<br />
<br />
Normally the .LDB is deleted when the last user exits the DB. &nbsp; But it is left if security prevents deleting it, or the DB has been flagged corrupt (so the the user can be identified).<br />
<br />
If your able to still use the DB after it's left, then there is not really an issue.<br />
<br />
Deleting of the .LDB was added long ago to speed up logins on Novell servers, but it's not actually required.<br />
<br />
Jim.
</div>


It can be.  It depends on if the user/process has delete rights on the file and directory.

Normally the .LDB is deleted when the last user exits the DB.   But it is left if security prevents deleting it, or the DB has been flagged corrupt (so the the user can be identified).

If your able to still use the DB after it's left, then there is not really an issue.

Deleting of the .LDB was added long ago to speed up logins on Novell servers, but it's not actually required.

Jim.

<div>
yes, I can still use the database afterwards, even with the LDB present.. &nbsp; &nbsp;And I can manually delete the file.
</div>


yes, I can still use the database afterwards, even with the LDB present..    And I can manually delete the file.

<div>
<div class="content wysiwyg-content">
I have an app that opens a OLEDB connection to access database. &nbsp;I close the connection and call &nbsp;Dispose. &nbsp;However, the LDB stills exist and does not go away until I close the app. &nbsp; Is this normal?
</div>
</div>


I have an app that opens a OLEDB connection to access database.  I close the connection and call  Dispose.  However, the LDB stills exist and does not go away until I close the app.   Is this normal?

Access - LDB lock file

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.