{"id":12040,"date":"2019-11-23T20:00:08","date_gmt":"2019-11-23T19:00:08","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=12040"},"modified":"2019-11-23T20:00:08","modified_gmt":"2019-11-23T19:00:08","slug":"addendum-fixes-for-access-error-3340-nov-22-2019","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/11\/23\/addendum-fixes-for-access-error-3340-nov-22-2019\/","title":{"rendered":"Addendum: Fixes for Access Error 3340 (Nov. 22, 2019)"},"content":{"rendered":"

[German<\/a>]What about the fixes for the access error '3340: query \"|\" is corrupted' triggered by the November 2019 security updates? Microsoft had announced further bug fixes as of November 22, 2019. <\/p>\n

<\/p>\n

Access Error '3340: Query \"|\" is corrupt' <\/h2>\n

\"\"Updates released for Patchday (November 12, 2019) for Microsoft Office cause Access to issue an access error '3340: Query \"|\" is corrupted\" during accessing databases. <\/p>\n

\"3340:  <\/p>\n

The error occurs in fact in all Access versions, with MSI and C2R installation as well as in the Access runtime. I had discussed the details in the blog post Office November 2019 Updates are causing Access Error 3340<\/a>. But Microsoft had released a hotfix for Access 2016 and promised further fixes for Access 2010\/2013 and the Click-to-Run versions for November 22, 2019 (see my blog post Fix for Error 3340 in Access 2016 (Update KB4484198)<\/a>). <\/p>\n

Changes: Office 365 fixed, the rest is delayed<\/h2>\n

First Microsoft announced the fixes for November 24, and December 10, 2019. Then the update with a fix (KB4484198<\/a>) for Access 2016 has been released on November 18, 2019. And Microsoft announced fixes for Access 2010\/2013 on November 22, 2019. But these fixes are now scheduled for November 29, 2019. However, the click-to-run versions for Office 365 Monthly Channel and Access 2016 C2R as well as Access 2019 (Version 1910) were provided with updates to fixe the bug on November 18, 2019. But this was already mentioned from reader as comments here within my blog. The table in this Microsoft article<\/a> now lists the following dates scheduled for the release of additional fixes.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Version<\/th>\nBuild<\/th>\nRelease Date<\/th>\nUpdate Link<\/th>\n<\/tr>\n<\/thead>\n
Access 2010<\/td>\n7241.5001<\/td>\nNovember 29, 2019 (estimated)<\/td>\n <\/td>\n<\/tr>\n
\n

Access 2013 MSI<\/p>\n

 <\/p>\n

Access 2013 C2R<\/p>\n<\/td>\n

5189.1002<\/td>\n\n

November 29, 2019 (estimated)<\/p>\n

December 10, 2019<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
Access 2016 MSI<\/td>\n4927.1002<\/td>\nNovember 18, 2019<\/td>\nKB4484198<\/a><\/td>\n<\/tr>\n
Access 2019 Volume License<\/td>\n—<\/td>\nDecember 10, 2019<\/td>\n <\/td>\n<\/tr>\n
Access for Office 365\/Access 2016 C2R\/Access 2019 (Version 1911)<\/td>\n12130.20390<\/td>\nNovember 18, 2019 (estimated)<\/td>\nUpdate aus Office-Anwendung<\/td>\n<\/tr>\n
Access for Office 365 Semi-Annual (1902)<\/td>\n\n

–<\/p>\n<\/td>\n

November 29, 2019 (estimated)<\/td>\n <\/td>\n<\/tr>\n
Access for Office 365 Semi-Annual <\/p>\n

Extended
(Version 1808)<\/p>\n<\/td>\n

—<\/td>\nDecember 10, 2019<\/td>\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

For Access for Office 365 and Access 2016\/2019 C2R, the update must be triggered from Office (menu File\/Account and then via the update command. This only works for the Monthly Update Channel (see table above). But you could switch from Semi-Annual to Monthly Update (as posted here<\/a>).<\/p>\n

Similar articles:<\/strong>
Office November 2019 Updates are causing Access Error 3340<\/a>
Fix for Error 3340 in Access 2016 (Update KB4484198)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]What about the fixes for the access error '3340: query \"|\" is corrupted' triggered by the November 2019 security updates? Microsoft had announced further bug fixes as of November 22, 2019.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,11,22],"tags":[1782,4,195],"class_list":["post-12040","post","type-post","status-publish","format-standard","hentry","category-issue","category-office","category-update","tag-access","tag-error","tag-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/12040","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=12040"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/12040\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=12040"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=12040"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=12040"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}