Forum Discussion
I cannot delete a ldb file in Microsoft Access
Thanks again!
Mike Peters
- Sasha_FroylandSep 14, 2024Copper Contributor
You can examine the contents of an .ldb (or .laccdb for Access 2007 and later) file to determine who is currently using the companion .mdb or .accdb file. The .ldb file is a lock file created when a Microsoft Access database is opened. It keeps track of users currently accessing the database in a shared environment.
Here's how you can gain insights from an .ldb or .laccdb file:
1. Using a Text Editor:
- You can open the .ldb or .laccdb file in a plain text editor like Notepad.
- The contents will show partial information about users accessing the database. Typically, you will see the computer names or usernames of individuals who have the database open.
- In older versions, such as Access 2003 or earlier, this is more readable, but in newer versions (like .laccdb), it might be less so due to file structure changes.
2. Using Microsoft Access:
- You can also check users currently accessing the database directly within Microsoft Access by navigating to the Database Tools tab and selecting Users under the Database Tools section (available only in some versions of Access). This will display the list of users.
3. Third-Party Tools:
- If you'd like to gain more detailed information, some third-party tools can analyze .ldb files and provide more structured data regarding which users are accessing the database and from which machines.
What Information You Can Expect:
- Usernames or machine names: Depending on your network setup and Access configuration, you can see either the user account names or the network machine names that have the database open.
- Record locking information: In some cases, the file can show which records are locked and being edited by users, depending on your locking strategy.
Keep in mind that the .ldb file only exists while the database is open in shared mode. Once all users exit the database, the .ldb file is deleted automatically.
- George_HepworthSep 14, 2024Silver Contributor
Thanks for sharing.
Your reply, while technically accurate, is not applicable to this problem. The problem is that there was a bug in a recent Office update, which was fixed in a more recent Office update. The OP acknowledged that applying that update resolved the OP's problem.
- Sasha_FroylandSep 15, 2024Copper ContributorThank you. I was aware. I just thought others might want to understand more about the LDB file.