If the Access database engine is processing the UPDATE query, the error occurs. It doesn’t matter if the query is against a table in the current database, a linked table, or a linked SQL Server table. While this is a drastic step, Microsoft repeated failed to release stable updates thereby causing more problems than they fix.Įrror 3340: “Query ‘qryName’ is corrupt”. To avoid such problems, disable automatic updates. This problem is even in the Semi-Annual Channel which is never supposed to include such poorly tested changes. Microsoft Office 365 subscriptions: Revert to an earlier version of Office Click-to-Run.Perpetual License (MSI) builds: Uninstall Office Updates.These are Microsoft support pages for reverting to a prior update depending on your Office license:
Microsoft published this new page with the latest information on this issue Error in Access when opening a database on a network file share Rolling Back to an Earlier Version If you have one of these builds, the only solution is to move back to an earlier build in the channel. Semi-Annual Enterprise Channel Version 2008, build 13127.21842.Semi-Annual Enterprise Channel Version 2102, build 13801.21086.Semi-Annual Enterprise Channel (Preview) Version 2108, build 14326.20692.Monthly Enterprise Channel Version 2109, build 14430.20380.Monthly Enterprise Channel Version 2110, build 14527.20340.These perpetual license updates introduced the problem : There will be a page added to the Fixes or workarounds for recent issues in Access (), which will be the place to go for updates. The update has only updated a small percentage of users, and we are pausing automatic updates. We are working on a fix, and will deliver it as quickly as This is due to the Decem(Patch Tuesday) update to Office. The problem was introduced by a security fix, so it impacts all active versions of Access. This can also impact workgroup security files (*.mdw) that also have their *.ldb lock file.This makes the database seem like it’s still being used. The Access lock file (*.laccdb or *.ldb for ACCDB and MDB databases respectively) is not being deleted after the last person exits the database.
The first person opening the database is successful but an exclusive lock is placed on the database preventing others from opening it.
Enter a new name or close the file that's open in another program. Customers reported errors like: Could not lock file (Error 3050)Ĭould not use 'Admin' (related to workgroup security) This prevents other users from opening the database and multiuser database sharing. Microsoft confirmed the Microsoft Office security update released on Tuesday (December 14, 2021) causes Microsoft Access databases on shared drives to be locked after users exit the database.