Office update possibly causing strange errors

Question

A client of mine has code which has been running error-free for years. However, recently strange errors have been surfacing in the running of the Access application. For example, a 3022 duplicate key error is being thrown on a table that has ID, Autonumber as the primary key. Another error 3340 (query is corrupt) is being thrown on a database table update query. Again, no changes have been made to the application for several years.

The client is running with Office 365, Access 2016. I suspect that some office updates have been occurring behind the scenes and this is the cause of the problems. Anyone else experience something like this ?

Answer 1

See below link to Microsoft support.

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

---

If this post answered or helped you find the answer to your question, please mark it as such for other Forum users knowledge.

Answer 2

Regarding Error 3340, this is but the latest bug caused by a series of flawed security updates that were released November 12th:

• Access 2010 – KB4484127
  
• Access 2013 – KB4484119
  
• Access 2016+ – KB4484113
  
• Access 2016+ – KB3085368

I asked the Access Dev Team and was assured that these are the only updates causing this issue.

You can read about the entire blunder by reviewing

https://www.devhut.net/2019/11/14/access-bug-error-3340-query-is-corrupt/

The article includes various workaround and fixes (for certain versions of Access).

The good news is that if you are running Access 2016, 2019 or Access 365, fixes are now available, you need only update.

The bad news is that if you are running 2010 or 2013 you are stuck with one of three options:

• Wait
• Uninstall the offending update(s)
• Run the code found at https://github.com/lauxjpn/CurruptQueryAccessWorkaround

---

Daniel Pineault, 2010-2019 Microsoft MVP
Professional Support: http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 3

Dan - re: 2010 or 2013.....are you indicating that if we are running Access 2016 via Office 365, all that is needed is to do an immediate UPDATE ?

Answer 4

Hey Daniel, they appear to have legitimate fixes out at Microsoft for all versions now.  I've been using the 2010 MSI fix at our site successfully.  There's a table of fixes for each version at 

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

-Bruce

Answer 5

Yes, normally updating O365 should solve the issue.

---

Daniel Pineault, 2010-2019 Microsoft MVP
Professional Support: http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 6

No, things haven't changed on that front, there are still certain version/deployment methods that still won't see a fix until December 10th.  A month to provide a fix to a critical issue.

---

Daniel Pineault, 2010-2019 Microsoft MVP
Professional Support: http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 7

Oops, my apologies, you are correct.  I did not see that some of the "release dates" for the listed fixes were future dates.  Yes, it's pretty sad that this is not a higher priority with Microsoft.  Particularly so when it appears that they have fixes for all the MSI versions but are not deploying it for click-to-run versions.

-Bruce

Answer 8

Dan - there is an Office 365 update with a version number of 1911 that just came out 12/3/2019.

I am hoping this update corrects the query problem and others as well.

Note: Build # is 12228.20332