Query UPDATE crash on all MS Access x64 after the November 12th patch

%3CLINGO-SUB%20id%3D%22lingo-sub-1007974%22%20slang%3D%22en-US%22%3EQuery%20UPDATE%20crash%20on%20all%20MS%20Access%20x64%20after%20the%20November%2012th%20patch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1007974%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20solve%20the%20Security%20Vulnerability%20CVE-2019-1402%20Microsof%20has%20released%26nbsp%3BKB4484127%20for%20Office%202010%2C%20KB4484119%20for%20Office%202013%20and%20KB4484113%20for%20Office%202016%20but%20after%20installing%20ALL%20QUERY%20UPDATE%20CRASH.%3C%2FP%3E%3CP%3EIt%20is%20possible%20to%20uninstall%20the%20KB%20and%20work%20fine%20again.%3C%2FP%3E%3CP%3EAny%20other%20solution%20in%20presence%20of%20KB%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1007974%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3E2013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1013646%22%20slang%3D%22en-US%22%3ERe%3A%20Query%20UPDATE%20crash%20on%20all%20MS%20Access%20x64%20after%20the%20November%2012th%20patch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1013646%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F457507%22%20target%3D%22_blank%22%3E%40cgentile%3C%2FA%3E%26nbsp%3BIf%20you%20can%20uninstall%20just%20go%20ahead%20and%20uninstall%20it...if%20not%20you%20have%20to%20%22replace%22%20your%20tables%20with%20queries%3C%2FP%3E%3CP%3EFor%20example%20you%20have%20a%20Table%20named%20myTable%20and%20normally%3C%2FP%3E%3CP%3EUPDATE%20myTable%20SET%20SomeField%20%3D%20SomeValue%3C%2FP%3E%3CP%3ENow%20either%3C%2FP%3E%3CP%3EUPDATE%20(SELECT%20*%20FROM%20myTable)%20SET%20SomeField%20%3D%20SomeValue%3C%2FP%3E%3CP%3Eor%3C%2FP%3E%3CP%3Erename%20myTable%20to%20e.g.%20myTable_tbl%20and%20create%20a%20query%20name%20myTable%20with%20SQL%20%3A%20SELECT%20*%20FROM%20myTable_tbl%3C%2FP%3E%3CP%3Eso%26nbsp%3B%3C%2FP%3E%3CP%3EUPDATE%20%3CFONT%20color%3D%22%23FF0000%22%3E%3CSTRONG%3EmyTable%3C%2FSTRONG%3E%20%3C%2FFONT%3ESET%20SomeField%20%3D%20SomeValue%20'(here%20mytable%20is%20the%20query%20that%20%22replaces%22%20the%20original%20myTable)%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

To solve the Security Vulnerability CVE-2019-1402 Microsof has released KB4484127 for Office 2010, KB4484119 for Office 2013 and KB4484113 for Office 2016 but after installing ALL QUERY UPDATE CRASH.

It is possible to uninstall the KB and work fine again.

Any other solution in presence of KB?

4 Replies
Highlighted

@cgentile If you can uninstall just go ahead and uninstall it...if not you have to "replace" your tables with queries

For example you have a Table named myTable and normally

UPDATE myTable SET SomeField = SomeValue

Now either

UPDATE (SELECT * FROM myTable) SET SomeField = SomeValue

or

rename myTable to e.g. myTable_tbl and create a query name myTable with SQL : SELECT * FROM myTable_tbl

so 

UPDATE myTable SET SomeField = SomeValue '(here mytable is the query that "replaces" the original myTable)

Highlighted

@tsgiannis this workaround works, however it's har to follow this path, having dozens of queries and VBA command, and some modules not directly accessible by myself, being protected by the software house who developed our ERP :cry:

Highlighted

STATUS: FIXED

This issue will be fixed for all versions:

Version                                                                        BuildRelease    Date

Access 2010

7242.5000

December 10, 2019

Access 2013

5197.1000

December 10, 2019

Access 2016 MSI

4939.1000

December 10, 2019

Access 2019 Volume License

10352.20054

December 10, 2019

Access for Office 365/Access 2019 (Version 1911)

12228.20152

November 24, 2019 (estimated)

 

https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f2163...

Highlighted

@cgentile I hope this issue can be pushed for way faster fix. We can't afford to have our application stopped for a moth.