Feb 20 2022 11:23 PM
Feb 20 2022 11:23 PM
My installation of MS Access (Office 365 subscription) suddenly lost the ability to compact and repair databases, after more than two years of working fine. I always get the error "Could not use [db]; file already in use."
Strangely, every time I attempt to compact and repair a database, an event appears in the system log seemingly not at all related to Access. It's Event 19, Source OED, Provider Name Intel-SST-OED, description "Check the remaining resource budget. Module exceeds resource budget, failed to AllocateFwCps, STATUS = Insufficient system resources exist to complete the API.."
Intel-SST is Intel Smart Sound Technology. Sound on the machine (Dell Inspiron 14 5000) works fine. Nothing else is obviously wrong. Why would compacting and repairing an Access database fail and cause an error in the audio driver?
Feb 20 2022 11:45 PM - edited Feb 20 2022 11:48 PM
Actually never mind the part about Event 19. Maybe that is just associated with the beep that happens when the compact-repair fails, and not related to the failure itself. (The beep sounds fine, but perhaps the audio driver is still sending an error). Still, I have a spontaneous loss of ability to compact and repair, after no obvious changes to the machine. The only recent automatic update was KB4023057, which seems to relate to the update engine itself and seems not much related to Access.
Feb 22 2022 10:26 PM - edited Feb 22 2022 10:58 PM
@isladogsI dread resorting to a laborious work-around for something that should work, and worked fine until recently.
Compacting from the command line, or compacting while the database is closed, both give the same error.
Feb 23 2022 01:11 AM - edited Feb 23 2022 01:12 AM
I can understand why you don't want to do laborious workrounds.
However, have a look at the very useful utility in this link: https://www.devhut.net/windows-explorer-ms-access-database-right-click-context-menu/
Over the years, Access has got less and less tolerant of issues that can cause corruption. Compacting an open database can indeed cause corruption in certain situations.
Perhaps your database has a lot of open connections when you try to compact? However, that wouldn't explain the errors occurring when run externally
Perhaps this is a side effect of the most recent Access bug? Which Access 365 build are you using?
Feb 23 2022 05:20 AM
Feb 23 2022 10:14 AM
Feb 24 2022 03:04 AM
I am glad to assist you.
You may operate some ordinary checks. Here are the things you must check before using the compact and repair method or any online repair tool.
Check out this thread as well, if this could help your issue somewhere:
Mar 08 2022 02:11 PM
Mar 08 2022 02:37 PMSolution
Mar 11 2022 10:27 AM