[AccessD] New KB breaks Access

[cjlabs]

Thanks for the info.   I just got "Query '' is corrupt" as an error on closing a form that has worked for years.   Replaced the 2 UPDATE statements in the procedure and it's working again.   Hate to think how many other forms are affected.



Carolyn Johnson


-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Wednesday, November 13, 2019 9:15 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] New KB breaks Access

Hi Ryan

I had this explanation:

This is not a Windows update problem, but a problem that was introduced with the November Patch Tuesday Office release.  A change to fix a security vulnerability causes some legitimate queries to be reported as corrupt.
Because the change was a security fix, it impacts ALL builds of Office, including 2010, 2013, 2016, 2019, and O365.

The bug has been fixed in all channels, but the timing of delivery will depend on what channel you are on.

For 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.
For O365, Monthly Channel, and Insiders, this will be fixed when the October fork is released, currently planned for Nov 24.

For 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.
If you can, you might want to hold off on updating until Dec 10.

The issue occurs for update queries against a single table with a criteria specified (so other types of queries shouldn't be impacted, nor any query that updates all rows of a table, nor a query that updates the result set of another query).
Given that, the simplest workaround in most cases is to change the update query to update another query that selects everything from the table, rather than updating the query directly.

I.e., if you have a query like: 

    UPDATE Table1 SET Table1.Field1 = "x" WHERE ([Table1].[Field2]=1);

Then, create a new query (Query1) defined as: 

    Select * from Table1;

and update your original query to: 

    UPDATE Query1 SET Query1.Field1 = "x" WHERE ([Query1].[Field2]=1);

The page "Fixes or workarounds for recent issues in Access": 

https://support.office.com/en-us/article/Fixes-or-workarounds-for-recent-issues-in-Access-54962069-14f4-4474-823a-ff7e5974a570

will be updated to reflect this.

/gustav

-----Oprindelig meddelelse-----
Fra: AccessD <accessd-bounces at databaseadvisors.com> På vegne af Ryan W
Sendt: 13. november 2019 16:07
Til: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Emne: [AccessD] New KB breaks Access

https://support.microsoft.com/en-us/help/4484119/security-update-for-office-2013-november-12-2019

This KB really broke our system this morning.  Just had to run around and uninstall it for everyone.

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com