If you can, you might want to hold off on updating until Dec 10. The bug has been fixed in all channels, but the timing of delivery will depend on what channel you are on.įor 2010, 2013, and 2016 MSI, and 2019 Volume License builds, and the O365 Semi-annual channel, the fix will be in the December Patch Tuesday build, Dec 10.įor O365, Monthly Channel, and Insiders, this will be fixed when the October fork is released, currently planned for Nov 24.įor the Semi-Annual channel, the bug was introduced in 11328.20468, which was released Nov 12, but doesn’t roll out to everyone all at once. A change to fix a security vulnerability causes some legitimate queries to be reported as corrupt.īecause the change was a security fix, it impacts ALL builds of Office, including 2010, 2013, 2016, 2019, and O365. This is not a Windows update problem, but a problem that was introduced with the November Patch Tuesday Office release. Create a new, empty table "Table1" with the default ID field and a Long Integer field "myint".Įxecute the following code in the VBA editor's Immediate Window:ĬurrentDb.Execute "UPDATE Table1 SET myint = 1 WHERE myint = 1"Įxpected result: The statement successfully finishes.Īctual result with one of the buggy updates installed: Run-time error 3340 occurs ("Query '' is corrupt").All of these patches have been released on Microsoft Update, so installing all pending Windows Updates should suffice: If you use an MSI version of Office, install the update matching your Office version.Office 365 Semi-Annual Targeted: Fixed in Build 11929.20494.
0 kommentar(er)
