42 responses on “Access – Bug – Error 3340 – Query is corrupt”

1. shlomi November 14, 2019 at 6:30 am

   my solution is to add to all the tables names the suffix “table” and create a query for each table with the original table name.
   that way, all the queries will update a query instead of the table directly.
   (i mean, to write a script that will do that of course)
   1. Danny K. Hunt December 4, 2019 at 10:22 am

      This absolutely works! Thank you so much for your comment.
2. Ebo November 14, 2019 at 1:21 pm

   Microsoft is aware of the issue, refer to https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec
   1. Alexandra Davis November 18, 2019 at 3:33 pm

      Yeah, they are aware, but not doing anything to actually help clients for weeks until they have the next bug injector/update ready.

      Here’s a fix that worked for me:
      @echo off
      cls
      rem https://stackoverflow.com/questions/58832269/getting-error-3340-query-is-corrupt-while-executing-queries-docmd-runsql/58833831#58833831

      REM KB4484127 (Office 2010)
      reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{91140000-0011-0000-0000-0000000FF1CE}
      if %errorlevel% equ 0 (
       "C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Oarpmany.exe" /removereleaseinpatch "{91140000-0011-0000-0000-0000000FF1CE}" "{F11D3275-8FE0-4ADB-B737-9766F9D0AD5B}" "1031" "0"
      )
      
      REM KB4484127 (Access 2010 Runtime)
      reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{90140000-001C-0000-0000-0000000FF1CE}
      if %errorlevel% equ 0 (
      "C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Oarpmany.exe" /removereleaseinpatch "{90140000-001C-0000-0000-0000000FF1CE}" "{F11D3275-8FE0-4ADB-B737-9766F9D0AD5B}" "1031" "0"
      )
      
      REM KB4484119 (Office 2013)
      reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{90150000-006E-0407-0000-0000000FF1CE}
      if %errorlevel% equ 0 (
      "C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\Oarpmany.exe" /removereleaseinpatch "{90150000-006E-0407-0000-0000000FF1CE}" "{3B7EE494-CBED-477C-AF90-8B8653C86985}" "1031" "0"
      )
      
      REM KB4484119 (Access 2013 Runtime)
      reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{90150000-001C-0000-0000-0000000FF1CE}
      if %errorlevel% equ 0 (
      "C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\Oarpmany.exe" /removereleaseinpatch "{90150000-001C-0000-0000-0000000FF1CE}" "{3B7EE494-CBED-477C-AF90-8B8653C86985}" "1031" "0"
      )
      
      REM Office Click-to-Run
      if exist "C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" (
      "C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.12130.20272
      )
      1. Daniel Pineault Post authorNovember 18, 2019 at 3:39 pm

         Yes, that was one the links I provided in my Other Resources section of the article. Definitely a worthwhile approach to be aware of as I fear this won’t be the last time we face this type of issue and need to rollback updates.
3. Luke Chung November 14, 2019 at 6:27 pm

   Hi Daniel,
   Thank you for your coverage on this. What a crazy last few days. Wrote up some additional information on this topic to include information on more situations where this is impacting customers (ACE/ADO, non-Access apps, web sites, etc.) and a link to download the Access 2007 runtime.

   http://fmsinc.com/MicrosoftAccess/Errors/query_is_corrupt/

   All the best,
4. Tom Kelley November 15, 2019 at 4:52 am

   In my case I linked another table to the one I was trying to update and it stopped the error message.
   In my case my payments table has a field named Folios in this case I needed to trim the number from 15 to 11 taking out the leading zeros. This update query gave me an error message. I have a table called YearType that has a field in my payments table that is related (Tax Year = YearType) when I linked the 2 tables the query worked. I only had 10 Update Queries so it was easy and I will not have to change anything after the fix, hopefully!
   1. Veerapoom November 18, 2019 at 6:36 am

      This is work for me. My environment has one front end database to link with many back end databases depends on my client that I would like to access. So it is impossible to change table name for all my back end databases. So you save my day. I just only create query to get all fields from table that related to update queries that have problem then add the new created query and link it together. The error message has gone. So I just modify update query in front end only. Thanks.
5. Michał Dziubek November 15, 2019 at 5:39 am

   Another workaround is using ADO to run query.
6. Evan Brydon November 15, 2019 at 10:46 am

   The code provided at https://github.com/lauxjpn/CurruptQueryAccessWorkaround has worked quickly and effectively in my case.

   We don’t have access to the security updates so removing them is not an option. Updating each and every bit of related SQL code also isn’t viable. The module provided by lauXjpn was an ideal solution in our case
7. Annaliese Dell November 15, 2019 at 10:47 am

   I have so many databases running connections to QuickBooks via QODBC using innumerable sql statements updating tables that it would take me until December 10th to rewrite them all. I can’t work. What am I supposed to do? I have click-to-run 2016 and tried rolling back to the last update but that didn’t work. Unbeliveable.
   1. Daniel Pineault Post authorNovember 15, 2019 at 11:00 am

      Did you see the recent update that update KB3085368 also needs to be uninstalled?
8. Bruce Jackson November 16, 2019 at 6:58 pm

   What a f… joke
   I did not have a problem until today 17/11/2019
   I have office 365 and none of those KB’s are listed as installed updates
   And what really pisses me off is that office 365 was updated yesterday-apparently with the bug attatched
   ms= more shitty stuff
9. Branislav M November 16, 2019 at 9:29 pm

   This is totally *””#*!! Imagine how many databases are there, how many teachers, students, business running. I’ve created tons of the databases and clients started appearing with “weird error”. And they need A MONTH to fix that??

   From version 2013 until today they virtually did nothing to fix existing issues in Access. Those “seven new things” are all cosmetic. They are just reselling the same product by the new name. But when it comes to breaking things up, they are very capable and on top of that, they need a month to fix it! What a customer support!

   No, I would not update any of my code nowhere. I am just redirecting clients to the Microsoft official webpage with this error. Also I am advising them to this article and to remove faulty updates (thanks for explaining).
10. R. Smith November 17, 2019 at 2:39 pm

    MS Office is worldwide business tool according to Ignite. Taking a month to fix something that affects nearly everybody worldwide who uses this tool via Access or Access 365 is negligent. Good luck making MS updates “required.”
11. worthrobbins November 17, 2019 at 2:56 pm

    Could someone explain what it takes to remove an update? I am running Office365, so I understand I need to get rid of KB4484113 and KB3085368. How do I remove?

    Thanks
    1. Daniel Pineault Post authorNovember 17, 2019 at 5:36 pm

       I have an article on the, refer to https://www.devhut.net/2017/10/04/microsoft-office-uninstall-an-update/

       But basically, you need to run a DOS command (yes, we’re living back in the 80’s!).

       officec2rclient.exe /update user updatetoversion=16.0.xxxx.yyyy

       where you need to replace 16.0.xxxx.yyyy with the exact build number you wish to implement. Since the bug was introduced in build 11328.20468, you need to pick something prior to that, perhaps 11328.20438.
       1. Alan Cossey November 18, 2019 at 7:44 am

          And you will need to switch off automatic updates using an Office client program to stop it reinstalling the offending update. To do this in Access, go to File then Account and then click on the Update Options button and disable updates there. Assuming Microsoft do the December 2019 monthly update correctly and supply us with the anticipated fix in there, you will then need to turn automatic updates on again in the same place at that time.

          Note that if you are on the Monthly (Targeted) channel for updates, you should get the necessary update around 24th November.
12. Chris November 18, 2019 at 7:20 am

    After a lot of test’s in my applications i’m sure that the only solution to the problem is to change the vba code from this:
    if you have a query like: UPDATE Table1 SET Table1.Field1 = “x” WHERE ([Table1].[Field2]=1);
    to that:
    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);
    Thank’s to you Daniel and Gustav Brock finally we can work!

    Ps I have send a nice one feedback as you said in Microsoft with all “French” words that i know
    Ps2 I’m sure that if i’m releasing version for my applications like Microsoft do, i’m gonna loose my Job.
    I wonder why Microsoft does’n to exactly the same!
    This is a F…. joke everytime with the Windows updates.
13. Alan Cossey November 18, 2019 at 7:45 am

    And you will need to switch off automatic updates using an Office client program to stop it reinstalling the offending update. To do this in Access, go to File then Account and then click on the Update Options button and disable updates there. Assuming Microsoft do the December 2019 monthly update correctly and supply us with the anticipated fix in there, you will then need to turn automatic updates on again in the same place at that time.

    Note that if you are on the Monthly (Targeted) channel for updates, you should get the necessary update around 24th November.
14. Peter November 18, 2019 at 7:53 am

    We run our entire business and financials on an access CRM that I’ve been developing for 15 years – it does pretty much everything apart from teleport us to jobs. Until this morning.
15. Chris November 18, 2019 at 8:30 pm

    Hi Daniel
    Just wanted to put out there that we hit this issue too across our organisation Monday morning. We are running Access as part of Office 365.
    We just did a File >> Account >> Office Updates this morning (19/11/2019 Australia Time) and the latest updates has fixed the issue across all machines so far.
    Appreciate other versions may not have the fix available yet but for us, this has worked (touch wood).
    I was knee deep in swear words and changing update queries to run on new query versions of tables and the Office Updates option has saved me hours…..
    Staff are back working which is the main thing but I’m wondering whether I should continue changing the queries anyway in a backup version to ‘double protect’ myself for future F Ups.
    I don’t think anyone of us expects Microsoft to know the knock on effects of every change they make but it sure used to a be a nicer relationship when they saw feedback and constructive criticism as a positive thing from its loyal user base not something they felt they needed to ignore or worse, door knock and try to silence those offering to help. I think its called Maturity but then I’ve seen that disappear over the 25+ years I’ve been working faster than the polar ice caps.
    To their credit this time, they have obviously responded quickly to the issue but I’m with you watching the unrecognised database format issue across a network dragging on and on. That’s a painful one.

    Good luck to all those affected with this and hope your skills to work the extra mile or the MS Fix comes along asap for your versions.
    Great website Daniel and keep up the enthusiasm and great help you always provide us.
16. Leanne November 19, 2019 at 12:41 pm

    Guys, I can’t see any of those security updates when I view my update history. Is it a windows update or an application update? I’ve only just had two of my staff computers throw up this error, and as we spend ALL day on our database in order to do our jobs, this is a HUGE problem.

    I can’t find the updates listed above to uninstall them. I am using Office 2016, installed from an office 365 online installation.

    I’m pretty close to RESETTING the two machines and reinstalling all our software, as it will be a darn sight quicker than having to rewrite all the update code!

    Can anyone provide any insight as to why I’m not seeing the updates listed at the top of this article, but still experiencing the same issue? It throws up the error Query ” is Corrupt.
17. H Gordon November 19, 2019 at 2:09 pm

    GREAT NEWS SOLVED!!!

    The Monthly 1910 update 12130.20390 released November 18, 2019 has the fix embedded in it. I ran the update on my 2016 office pro click to run version and the problem was resolved.
18. Andrey November 20, 2019 at 6:20 am

    What helped me today (Nov 20th) with my Office 2016 is updating to the latest version of Nov 18th:

    rum cmd
    cd C:\Program Files\Common Files\Microsoft Shared\ClickToRun
    officec2rclient.exe /update user updatetoversion=16.0.12130.20390

    After installation the bug has gone.
    1. Daniel Pineault Post authorNovember 20, 2019 at 8:05 am

       For those not comfortable using DOS command, since you are simply updating to the most recent version, you can use the UI to perform the update:

       File -> Account -> Update Options -> Update Now
       1. GYULA November 21, 2019 at 8:05 pm

          What if I don’t have the Update Options button? I have office 365 subscription came installed on the Dell laptop I bought…
          1. Daniel Pineault Post authorNovember 21, 2019 at 8:29 pm

             I sent your question along to the Access Dev Team and they were kind enough to answer:

             “If they don’t have the Update Options button, it is probably a Windows Store install. That is likely if it came pre-installed.
             You can confirm this by checking the ‘About Access’ box where it lists the version/build, it should say ‘Microsoft Store’ after the build number.

             If that’s the case, to get the update, go to the Microsoft Store, click on the … in the upper right corner, and choose Downloads and Updates, and that should pick up the update.”

             Could you look into the matter and post back either way as it will help others facing the same issue.

             Thank you.
             1. GYULA November 21, 2019 at 8:39 pm

                I did exactly that a few minutes ago and it worked.
                Some notes:
                The Get Updates did not show any of the Access/Excel/Office etc updates in the list I clicked update all, anyways. I clicked Get Updates again, hoping it would now show the Access 2016 in the list…it didn’t.
                BUT, when I went and checked MS Access-File-Account: it was updated to 20390! So even if it does not show up on the Microsoft Store get Updates list, it sneakily gets updated in the background…:-)

                Thanks for getting back to me!
                Gyula
19. Scot VanWoert November 22, 2019 at 9:08 am

    We are running version 1902 and could not uninstall the update on many computers.
    Microsoft sent me this and it works:

    1. In an Office application, (Word, Excel, Outlook, etc.) Select File – Account (or Office Account), then click Update Options and select Disable Updates
    a. If you don’t do this, Office will just update again in the near future, and until the patch is rolled out, we don’t want that.
    2. Close all of your Office apps
    3. Open a Command Prompt
    a. Click Start, type CMD, and right click the Command Prompt app that appears, and select “Run as Administrator”
    4. In the command prompt, type:
    1. “C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe” /update user updatetoversion=16.0.11328.20438
    a. This version was the last build as of October 8th. If you believe the version you need is even older, you could try using 16.0.11328.20420 (the version before that).
    i. The list of all versions can be found here: https://docs.microsoft.com/en-us/officeupdates/update-history-office365-proplus-by-date?redirectSourcePath=%252fen-us%252farticle%252fversion-and-build-numbers-of-update-channel-releases-ae942449-1fca-4484-898b-a933ea23def7
    1. Daniel Pineault Post authorNovember 22, 2019 at 2:22 pm

       Yes, that is one of the solutions mentioned above. You disable automatic updates and then reverted your installation to the build prior to this faulty update.
20. TJH November 22, 2019 at 9:33 am

    This error hit me today.
    Thanks to devhut.net/2019/11/14/access-bug-error-3340-query-is-corrupt the fix was easy – manually force the update to Office356 File -> Account -> Update Options -> Update Now and it’s gone away.
    But I have to do this on all our machines.
    If MS has known it was a problem I agree heads should roll for not immediately stopping the updates – unless they had identified a security threat even bigger than the problem of crashing everyone’s databases.
21. Bruce Jackson November 23, 2019 at 1:15 am

    I have spent the last few months moving all data structure to sql server (Access front end),something forced upon me by the other major problem “unrecognised database format issue’ which I don’t think ms are going to fix
    the “query is corrupt” did not affect any of this development database,so seems moving to sql (expensive as that is) may have been a blessing of sorts
    The production copy has been impacted by the “query is corrupt”,and I am still months away from rolling out the sql backend
    of course who’s to say they wont screw sql server up as well
    I am really at the mercy of MS
22. David Boccabella November 24, 2019 at 8:23 pm

    Currently running our entire high volume order entry, and out lab management system on MS Access – it was a delight where our entire lab and customer service staff went down with this error.

    I ran the fix of appending _Table to the table names however there is still a LOT of code that won’t run because I use SQL Executes.

    Thanks you MS for this nightmare.
23. Branislav Mihaljev November 24, 2019 at 8:44 pm

    I see they have fixed the issue in some builds:

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

    But they messed things again with versions. On the Account screen I see:

    Build 12130.20410

    And when I click About Access:

    Build 12130.20232

    (I just run a manual update and got different versions)
24. Dave Holbon November 25, 2019 at 5:28 am

    I’ve just updated to Windows 10 19025 (slow lane) an the fix I had in place for the MSI version of Office 2016 was removed and bug returned. Luckily I had previously downloaded this fix so just applied it again ace2016-kb4484198-fullfile-x86-glb.exe .
25. Jennifer L Jeffcoat November 25, 2019 at 12:32 pm

    I installed the update for my version this morning…the “fix” was released Friday…it still does not work I get the Query corrupt error…I’m on version 1902 build 11328.20480 (this is the “fix”, the prior version which was the one that introduced the error to my Access was 11328.20468…anyone else running into this same problem with this version? Two of us in my office spent all day Thursday trying to figure out a solution to this issue without having to change the query itself…I could not get any prior version to work and run that Access file from my computer, it showed I had installed the prior version and was active in my account settings, but still got that query is corrupt error. I got the update to work on a newer version of 365 than mine and I got it to work on the 2010 versions in our office…but still no solution for mine…extremely frustrating…and I contacted Microsoft, got transferred 4 times and the last one wanted to transfer me back to the prior one so I gave up.
26. Branislav Mihaljev November 25, 2019 at 8:22 pm

    Agony for most non-tech users continues. I got contacted by many people and I simply gave them Microsoft web page link. Most of them were UNABLE to fix the faulty update issue. I am emailing almost a whole day about this. Some did and the issue returned. After so many faulty Windows updates I guess they at Microsoft are going to mess the Office completely.
    I was just talking with one user who knows a bit more than a vanilla user. He was able to fix one computer but was unable to fix another user.
    We were working on an Access/SQL program that is in use for oil rig platforms inspection. Now imagine they send an inspector to the inspection (with organized chopper flight and so on) where he got “Query is corrupt” message? If I told them to remove one of the updates, they are thinking I am crazy and “I am afraid to break something else”.
    I am thinking that the best advice I can give and to avoid such situations (including faulty Windows update – check “Ask Woody”) is to turn off updates completely and just update the Defender from time to time manually.
    They could just make an update that will remove faulty update(s) within an hour, but no, they created a total mess.
27. Dave Holbon November 28, 2019 at 8:48 am

    I’ve just updated to Windows 10 19033.1 and this time it either left the fix in place or reinstalled it.
    So the fix must be out there somewhere.
    1. Daniel Pineault Post authorNovember 28, 2019 at 8:55 am

       Yes, for some versions an update is available to fix this issue. So automatic update should resolve the issue for some users, but not all. Some versions are still only scheduled to get an update December 10th, so it all comes down to which version you are running.
28. Alexandre Neves November 29, 2019 at 5:23 pm

    Não altere as tabelas nem consultas, use apenas o meu código e adapte a chamada de execução
    Sub UPDATE(strNomeTab As String, strInstrucaoSET As String, Optional MostraQtAlterados As Boolean = False)
    ‘————————————————————–‘
    ‘ código criado por Alexandre Neves, do Fórum MaximoAccess ‘
    ‘ utilize o código livremente mas mantenha os créditos ‘
    ‘————————————————————–‘
    ‘Exemplo com opção de mostrar quantidade de registos afectados
    ‘Call UPDATE(“Tabela”,”Campo=X”,True) em vez de UPDATE Tabela SET Campo=X
    ‘Exemplo com opção de mostrar quantidade de registos afectados
    ‘Call UPDATE(“Tabela”,”Campo=X”) em vez de UPDATE Tabela SET Campo=X
    Dim qdf As QueryDef
    Set qdf = CurrentDb.CreateQueryDef(“qdf” & strNomeTab, “SELECT * FROM ” & strNomeTab)
    If MostraQtAlterados Then
    With CurrentDb
    .Execute “UPDATE qdf” & strNomeTab & ” SET ” & strInstrucaoSET
    MsgBox .RecordsAffected
    End With
    Else
    CurrentDb.Execute “UPDATE qdf” & strNomeTab & ” SET ” & strInstrucaoSET
    End If
    CurrentDb.Execute “DROP TABLE qdf” & strNomeTab
    End Sub
29. Mark Potter December 3, 2019 at 7:25 am

    I think MS will have done more damage to the Access community and customer base than they realise.
    I’ve spent much of the last 25 years creating bespoke Access based systems for small and medium sized businesses and corporates with many of these solutions considered ‘business critical’. Organisations can sometimes dislike Access for various technical reasons that arise, very often, from a lack of understanding and experience with professionally built and deployed Access systems. (I.T. Departments seem to have a particular dislike of Access where they’ve previously inherited poorly built systems from non-skilled developers.)
    THIS situation from MS plays right into such thinking and has significantly raised concerns amongst my user base. I now have clients insisting on a move away from Access for some mission critical operations that have been stable and reliable for many years but have recently seen Windows 10 causing data corruptions and Windows Updates crippling systems as effectively as hackers might. They haven’t seen such ‘weaknesses’ in other systems and simple don’t find it acceptable.
    So my point is these serious attacks on the reliability and stability of MS Access are extremely damaging, not just to Microsoft’s offering but to my credibility (and profitability) as a solution provider… and possibly 1000s like me. It might not ‘feel’ so terrible if the issues were caused by external factors but for them to be from within is unfathomable. The lack of adequate response totally unacceptable.
    Whilst I feel like I need to vent some frustration and reach out to others in the community it also feels like a total waste of time because it will have no effect, whatsoever, on Microsoft who certainly give the appearance of not caring two hoots about the impact of these screwups on their users and loyal professionals.

    Yours
    Mark P.
    One sincerely annoyed and frustrated Access Developer