{"id":12083,"date":"2019-11-27T23:09:00","date_gmt":"2019-11-27T21:09:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=12083"},"modified":"2019-11-27T22:09:10","modified_gmt":"2019-11-27T21:09:10","slug":"2-nachtrag-zu-fixes-fr-access-fehler-3340-27-11-2019","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/11\/27\/2-nachtrag-zu-fixes-fr-access-fehler-3340-27-11-2019\/","title":{"rendered":"Fixes for Access 2010\/2013 Error 3340"},"content":{"rendered":"

[German<\/a>]Today a second addendum regarding the fixes for the access error '3340: query \"|\" is corrupted' triggered by the November 2019 security updates? This is the third time Microsoft has postponed bug fix dates. This time fixes for Access 2010\/2013 in the MSI version were preferred.<\/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> and the blog post Addendum: Fixes for Access Error 3340 (Nov. 22, 2019)<\/a>). Microsoft announced fixes for Access 2010\/2013 (MSI install) for November 29, 2019. <\/p>\n

Fixes for Access 2010\/2013 (MSI) available<\/h2>\n

The tabelle shown within this Microsoft article<\/a> lists again changed dates for the release of fixes. <\/p>\n\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.5000<\/td>\nNovember 27, 2019 <\/td>\nKB2986256<\/a><\/td>\n<\/tr>\n
Access 2013 MSI <\/p>\n

Access 2013 C2R<\/td>\n

5189.1002<\/p>\n

5197.1000<\/td>\n

November 27, 2019 December 10, 2019<\/td>\nKB2965317<\/a><\/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>\n10352.20042<\/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 <\/td>\nUpdate aus Office-Anwendung<\/td>\n<\/tr>\n
Access for Office 365 Semi-Annual (1902)<\/td>\n11328.20480<\/td>\nNovember 22, 2019 <\/td>\nUpdate aus Office-Anwendung<\/td>\n<\/tr>\n
Access for Office 365 Semi-Annual Targeted (Version 1808)<\/td>\n11929.20494<\/td>\nNovember 22, 2019 <\/td>\nUpdate aus Office-Anwendung<\/td>\n<\/tr>\n
Access for Office 365 (Microsoft Store version)<\/td>\n12130.20390<\/td>\nNovember 18, 2019<\/td>\n\u00dcber Microsoft Store<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

All Click-to-Run versions (except Access 2016 C2R) are fixed now. The same applies to the MSI installations from Access 2010 to 2016. Now Access 2016 C2R and Access 2019 Volume License is now pending for a fix as of December 10, 2019. <\/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>
Addendum: Fixes for Access Error 3340 (Nov. 22, 2019)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Today a second addendum regarding the fixes for the access error '3340: query \"|\" is corrupted' triggered by the November 2019 security updates? This is the third time Microsoft has postponed bug fix dates. This time fixes for Access 2010\/2013 … Continue reading →<\/span><\/a><\/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,399],"class_list":["post-12083","post","type-post","status-publish","format-standard","hentry","category-issue","category-office","category-update","tag-access","tag-fix"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/12083","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=12083"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/12083\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=12083"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=12083"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=12083"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}