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.
Aleks R
shared this idea
The fix for this is coming for all affected builds.
The page here: https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec
Will be updated if we can get fixed builds out sooner than currently scheduled.
49 comments
-
Tim Snoots
commented
Please issue an immediate patch for this in for versions of Office. I bet if a bug caused all UPDATE queries issued to SQL Server to fail that it would be patched in less than a month!
-
Aleks R
commented
We have worked with hundreds of clients to remove the update. Some of our clients could follow our instructions to do it themselves, but many don't feel comfortable, so we work with them.
Now we are working with many clients a second time because their system setup did not allow a pause of automatic updates, and they got the update again. HOW? How are the problem updates still being delivered to clients?? Waiting for a patch for already updated systems is ridiculous, but still delivering a known faulty update?
Our own little shop has spent over 150 man hours dealing with it, and our clients have lost who knows how many hours not being able to use crucial systems.
Does Microsoft have a clue as to how big a problem this is?
-
me
commented
Disgraceful to have this happen to so many installations. Disgusting to have to wait until December for a solution. Lost confidence in Microsoft's ability to look after us.
-
Anonymous
commented
The fix can not wait 1 month to be released... Microsoft needs to do that ASAP...
-
Matt Luckham
commented
We have 1,200 installation and we are drowning in support. This needs to be fixed NOW! Why can they not send an update out?
-
Leon Kernan
commented
Walked into work this morning to find out critical applications were broken. These are 3rd party purchased apps, not something we have code for!
Thank goodness the update removed cleanly.
-
Anonymous
commented
Our clients are unable to run their businesses. We need a fix NOW, not next month.
-
John
commented
We're hurting here. Please give this fix #1 priority! Please!
-
CRM
commented
We need an URGENT fix! NOW - not in December!
-
Anonymous
commented
completely inacceptable, the workaround to replace all query is just a joke, what we suppose to do, go over thousands of queries and redeploy every customer. Instead can microsoft just remove this automatic update so they have time to do their job right ?
-
Aleks R
commented
Jan Bečka: Yes, we have had two clients on semi-annual channel need to revert their version so far.
-
Jan Bečka commented
Hi Guys, Is this affecting Semi-Annual channel as well ?
-
Tyler
commented
This has impacted 10,000+ of our clients all running Access ERP applications for their business. It has put business at a 100% stand-still, losing all ability to access, enter, and view data. We need am immediate patch as the proposed solutions is absolutely unfeasible to manage to the scale in which Access applications are distributed. An unprecedented overlook by the Microsoft Development Team. Our phone has been ringing off the hook for roughly 2 days now!
We need an URGENT fix!
-
Dolly
commented
This isn't the first bug to slip by into production and impact millions. Things need to change this is completely unacceptable.
Why haven't you rolled back the update until you have a proper update that doesn't break things! This isn't a hard concept to understand and MS has done so previously, so it's not hard to do.
Someone should be fired for this.
-
Anonymous
commented
Wouldn't it be nice if Microsoft started treating MS Access as a fully developed product that is critical to many businesses? Can you imagine the uproar if SQL Server broke and they said that they would fix it for a month!!!!!!!!
-
Christian
commented
We need an urgent fix!!! This is affecting thousands of user!!
-
James Muka
commented
Aleks R: Thank you!
-
Raymond
commented
Our company was unable to function for half a day. A lot of extra work and costs. A better qualty control is absolutely necessary!!
-
Tyler
commented
We have roughly 10,000+ Clients that all are fully reliant on Microsoft Access (2010, 2016, 2019, O365 ProPlus) and all have been effected. Our phone are ringing off the hook as their businesses are at a standstill. We need AN URGENT fix!
In the event we uninstall the patch, we need assurance on a viable plan moving forward that future updates will not cause the same issue. This is unprecedented and without question that largest IT flaw we have seen in years, potentially crippling business.
-
Momo
commented
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.