Summary
This is a known bug caused by the Office updates released on November 12, 2019. The bug affects all versions of Access currently supported by Microsoft (from Access 2010 to 365).
This bug has been fixed.
- If you use a C2R (Click-to-Run) version of Office, use "Update now":
- Access 2010 C2R: Fixed in Build 7243.5000
- Access 2013 C2R: Fixed in Build 5197.1000
- Access 2016 C2R: Fixed in Build 12130.20390
- Access 2019 (v1910): Fixed in Build 12130.20390
- Access 2019 (Volume License): Fixed in Build 10353.20037
- Office 365 Monthly Channel: Fixed in Build 12130.20390
- Office 365 Semi-Annual: Fixed in Build 11328.20480
- Office 365 Semi-Annual Extended: Fixed in Build 10730.20422
- Office 365 Semi-Annual Targeted: Fixed in Build 11929.20494
- If you use an MSI version of Office, install the update matching your Office version. All of these patches have been released on Microsoft Update, so installing all pending Windows Updates should suffice:
Example
Here is a minimal repro example:
- Create a new Access database.
- Create a new, empty table "Table1" with the default ID field and a Long Integer field "myint".
Execute the following code in the VBA editor's Immediate Window:
CurrentDb.Execute "UPDATE Table1 SET myint = 1 WHERE myint = 1"
Expected result: The statement successfully finishes.
Actual result with one of the buggy updates installed: Run-time error 3340 occurs ("Query '' is corrupt").
Related links:
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…