Bug fix needed for MS Access Update queries with WHERE clause
Bug fix needed urgently!
11/12/19 Office ProPlus 365 Update broke Access UPDATE query with WHERE Clause.
Queries without WHERE clause still work.
Can be recreated in new mdb or accdb database with single table. Write a query that tries to Update a value in the table. If the query has a Where clause, the query fails with a message of:
Query 'qryName' is corrupt
The database is NOT corrupt. Moving the database to another machine that has not been updated with today's Update (16.0.11328.20468, depending on Channel type), allows the query to work.
Query fails whether table is in the local database or the table is linked.
We could get around the problem by simply adding a table to all the affected queries. Just adding an unrelated random table to the query will stop the error.
Oh, and for those of you removing Security Updates -- make sure you turn off the flag to install Office Updates automatically BEFORE you remove the KB. Else, the offending KB will start re-installing immediately.
We have removed KBs from dozens of clients today, and will likely have to do the same thing again tomorrow because of this automatic updating.
I wonder if Microsoft has a clue as to the magnitude of this problem. Replacing tables with queries as a work-around??
James Muka: For our 365 clients, we have followed the steps to revert the entire version, found here: https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic
Incredibly annoying to have to do it, and to lose all the actual benefits of the updates, but it's actually easy to do.
James Muka commented
Rolling back the "Un-Security Updates" works for all Access version except for 365. This is major issue! We really need a solution fast.
Ben Sacheri commented
This is affecting a lot of people! Ugh.
Klaus Oberdalhoff commented
A quick hotfix really would be better than the needed uninstall of that "Un-Security Update"
Anders Ebro (TheSmileyCoder) commented
Here is the support article about it:
Note that the error associated with this is 3340.
For Access 2010, uninstalling KB4484127 fixes it.
For Click-to-run versions, reverting to the previous version fixes it. Unfortunately, that means that you lose all the now-documented security patches in the update, so I truly hope Microsoft patches this.
James Muka commented
This bug needs to be immediately fixed! We can't wait until December 10, 2019.
Please Please immediately release the fix now.
Same problem here. It's a huge problem, easily reproducible.