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
51 comments
-
edwards142 commented
Last few months back Microsoft has released an updates for MS Access keeps crashing frequently:
In many of the PCs it is found that, these updates will be automatically gets installed and starts troubling you. When I encountered with the same issue I have found all of a sudden my Access query is got corrupted. It starts throwing following error:
Error name: Query is corrupt
Error code: Error 3340To catch complete detail on how to fix this query corruption issue, you can easily get help from this post:
http://www.accessrepairnrecovery.com/blog/fix-corrupt-ms-access-query
-
Joakim Dalby
commented
Today my Access 2013 can do sql update in a table again, I did a Office update inside Access under Account.
-
Aleks R
commented
It blows my mind that users are still getting these faulty updates. We are still working with clients who are getting the error for the first time. Sure, in most cases, it's an easy fix, often a KB install. But if Microsoft has the ability to push updates on users, then WHY are they not also pushing out the patch KBs to applicable versions? So many man hours lost to this debacle, and though it has eased up, it's still going on.
-
Janin Lord
commented
THANKS ALOT PAL ! ...Here again... Fun is still with the old DOS when it comes to talk with a computer. You made my day... And 40 bucks for troubleshooting fees. LOL. ;-) Yeah... Just 40...
-
Jan Bečka commented
This is EPIC FAIL!!! unfortunately not over for us, because new update 12130.20410 failing to install with another bug https://support.microsoft.com/cs-cz/help/4532996/office-365-version-1910-updates-in-configmgr-do-not-download-or-apply
Last fourteen days is like a nightmare. I won't work with tools supported like that, time look for other options not Microsoft at all.
-
Aleks R
commented
@Dolly, thank you! A co-worker found the command prompt thing, but we were afraid to use a client as a guinea pig without having tried it in-house first. Fortunately, it did work. Thanks!
-
Dolly
commented
@Lapointe, @Aleks R
That build number implies Access 2013 C2R, so you have to use the officec2rclient.exe command to revert your installation to a prior build (before this whole issue surfaced). So open a command prompt, swicth into the officec2rclient.exe directory and run the command. Something like:
cd C:\Program Files\Common Files\Microsoft Shared\ClickToRun
officec2rclient.exe /update user updatetoversion=15.0.5179.1000You'd think Microsoft, at the very least, would have this type of information on their fixes page.
Don't forget to turn off automatic updates!
Also, just for clarification purposes for anyone actually trying to understand this mess with Access 2013, build 15.0.5189.1000 (https://docs.microsoft.com/en-us/officeupdates/update-history-office-2013) installed KB4527848 (https://support.microsoft.com/en-us/help/4527848/november-2019-updates-for-microsoft-office) which included, for Office 2013, KB4484119 (our problematic update!!!). So in fact the KB was installed, it's just that Microsoft has made it impossible for anyone to easily view this.
-
Lapointe
commented
I'm born at 1959-11-24... I have a dev company since 1980 and will be in holidays at nov 30 for rest of life.
I do access from V1, and thousand query later I can't belive the solution M$ propose... They say... Access is a toy and you can just modify 2 or 3 query adding....As Aleks R said
I have up to hundred computers installed with acc 2013.
On some of them KB was uninstallable, because was installed
On some others this kb seem to be not installed but "query corrupt" problem exist on.
In fact these computer have been installed directly with 5189.1000 release of access, so no updates are avalaible or uninstallable.
What can we do to say m$ t's enought to be working graciously for then? Group action ?
They know there is a real problem in these updates but they continue to push them… Who can do that with is clients else m$? -
Aleks R
commented
Does anyone know of a fix for Access 2013 users with a version of 15.0.5189.1000?
This version does not HAVE a KB to uninstall. KB4484119 is not installed.
Edit: I don't mean changing our Update queries. That's not a viable fix.
-
Markus
commented
Is Access just a toy for Microsoft??? It is not acceptable to wait so long for a fix !! Our Business is down, the workaround is a joke. Fix it now
-
Aleks R
commented
We have been logging on to clients systems and uninstalling KBs or reverting C2R versions almost non-stop since last Wednesday.
It's good that Microsoft has published updates for the Monthly Channel C2R and for non-C2R 2016. The fixes came about four days too late in my opinion, but it's good that they came.
But now they have pushed BACK the timeline for other versions' fixes.
We expected new KBs for A2010 and A2013 today. The timeline now says next Friday.
The timeline for C2R Semi-Annual Channel fixes was Monday, 11/25. Now, it's Friday, 11/29.I used to have little faith in Microsoft. Now I have none.
Oh, how I wish we could charge Microsoft for the hundreds of man hours we have lost due to their mistakes. And for the who knows how many hours our clients have lost.
-
Eugene
commented
Well, our production was crippled because of this issue, and we are not changing all the UPDATE queries, it is impractical. Possibly we should invest in some other DB system. Access 2010.
-
John Jasper
commented
Access 2013 – update KB4484119 is causing the "query is corrupt" on mine. It seems to be caused by selecting a single table. My simple fix was to open the query in design view and select the "show table" and pick (add) a second table. The second table does not need to be linked.
-
Stephan
commented
In over 15 years of Access development I haven't seen a screw up to this degree. I have clients that have limited or significantly slowed business operations for the past week because of this, I don't understand why Microsoft hasn't put this at the top of their priority list and fixed it yesterday, because I know I'm going to get more calls today.
-
William W.
commented
Microsoft wake up there are 1000's of users that cannot update or enter data due to your update.
You should put everything to side and have a update out by tomorrow. I have customers that are waiting for well over a week to take care of this. I will net create Queries and call the query instead of the table. It will take me days!
What a disgrace!!!!
-
Paul O
commented
It is unconscionable that a bug of this magnitude was allowed to be released. Worse that there is no simple way to roll back a bad update like this.
Faux pas like this create serious doubt about Microsoft and its products. What the hell is going on with QA at Microsoft?
-
Aleks R
commented
Anonymous: Thanks. Yes, we have been following the same instructions.
My question was for later.
We have a computer in-house that we reverted from 12130.20344 to 12130.20272.
Now, when I click "Update Now" in an Office product on that machine, it says that I'm up-to-date.
Even though a newer version, 12130.20390, is available as of last night. Our products are working fine in the 12130.20272, but at some point, I'd like to get the machine (and our clients with whom we've worked) to the current version that has patches for the now-published security holes.I was wondering if anyone had previously done a manual revert, and then later got the product back to current. How? Thanks!
-
Anonymous
commented
Aleks R
We've been using this procedure to roll back click to run installs.
https://support.microsoft.com/en-au/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clicThe config file that we're using for office 2016 is this:
<Configuration>
<Updates Enabled="TRUE" TargetVersion="16.0.12130.20272" />
</Configuration>Otherwise we're following the directions and then turning off automatic updates in office.
-
Aleks R
commented
We have verified that installing KB4484198 does work for Access 2016 non-click-to-runs.
We have verified that running "Update Now" for Access 2016 click-to-run 12130.20344 does work.
So that's good.
We are still actively uninstalling KBs for our A2013 and A2010 clients, and rolling back versions for those click-to-runs on the semi-annual channel.
Next we have to figure out how to get those click-to-run clients whose versions we rolled back to be on the current version again. When you pick "Update Now" on those guys, the system thinks they're up-to-date (or as up-to-date as the System Administrator says they may be).
Does anyone reading this have experience with Undoing a Version Rollback on Click-to-run Office?
-
wilo
commented
i am happy to see that the fix finally came out today for 2016
GOOD JOB EBO!!