Lccmdb and ldb files

When and Access program is opened it creates a "lock file" with the same name as the parent file but a different extension. This file shows access that either the parent program is opened or closed with problems.

• .mdb files generate file with .ldb extension (eg. CCMDB.accdb will generate file CCMDB.ldb)
• .accdb files generate a file with .lccmdb extension (eg. PHI Loader.accdb will generate file PHI Loader.lccdb)

For the most part these files can be ignored. In our context they are relevant only if you are going to move the parent file; a parent file should not be moved until the lock file is gone. To get rid of the lock file, give Access a chance to resolve problems by doing the following.

Instructions how to remove lock files

1. check file properties (right click) ownership
   • click on security tab
     • click on Advance tab
       • click on Owner tab
2. get the owner to close out of any open parent program
   • the error often happens during sending; in that case, the owner of the file should close out of CCMDB.accdb, follow Breaking out of a frozen program to make sure no hanging instances remain, then open CCMDB.accdb again and send again
3. if lock file still there, get them to open and then close parent program
4. if lock file still there, end the task: open task manager (ctrl-shift-esc), find any Microsoft Access entries, right-click, end task them (make sure you don't also have another access program open at the same time)
5. if lock file still there, get them to re-boot their computer
6. if lock file still there, get them to try to delete the file manually
7. if lock file still there and it is on a network drive, send a ticket to the helpdesk to get the file deleted

rights

• 2025-07-22 - email saying "permissions set nominally" - whatever that means... Task# 638500 - Access Lock File Permission Issue — Request for Folder ACL Adjustment | TTENBERGEN@hsc.mb.ca for Service Request REQ496796
• 2025-06-30 - suspect problem is that the lock files appear to be generated with single user ownership that others then can't delete; sent email to service desk to get folder rights tweaked to allow our entire team to delete these.