{"id":16924,"date":"2019-11-19T06:32:59","date_gmt":"2019-11-19T14:32:59","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2019\/11\/19\/news-10661\/"},"modified":"2019-11-19T06:32:59","modified_gmt":"2019-11-19T14:32:59","slug":"news-10661","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2019\/11\/19\/news-10661\/","title":{"rendered":"Microsoft starts releasing fixes for Access bugs introduced in Office security patches this month"},"content":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Tue, 19 Nov 2019 06:09:00 -0800<\/strong><\/p>\n

Although we\u2019ve been promised no \u201cC\u201d or \u201cD\u201d week second cumulative updates for the rest of the year \u2014\u00a0<\/span>at least for Windows<\/span><\/a>\u00a0\u2014 Microsoft has acknowledged a bug it created in last week\u2019s Patch Tuesday Office patches, and now promises that it\u2019ll update the bad fixes on most machines this week or next. Those are “C” week and “D” week, respectively.<\/span><\/p>\n

The cause du jour: a bug in all of this month\u2019s Office security patches that throws an error in Access saying, \u201cQuery xxxx is corrupt,\u201d when in fact the query in question is just fine. Microsoft describes the erroneous error message on its<\/span> Office Support site<\/span><\/a>:<\/span><\/p>\n

When attempting to run an Update query, it may not run and displays the error: “Query ‘query name’ is corrupt”.\u00a0<\/span><\/p>\n

This will occur for an Update query that:<\/span><\/p>\n

This issue impacts all supported builds of Access.<\/span><\/p>\n

The issue was introduced on November 12, 2019<\/span><\/p>\n

It\u2019s the same bug I discussed in <\/span>Woody on Windows<\/span><\/a> on Nov. 13. It just took Microsoft a week to acknowledge the error.<\/span><\/p>\n

There\u2019s a new cumulative update for Office 2016 (the installed version, not the Click-to-Run) released yesterday, <\/span>KB 4484198<\/span><\/a>, that claims to fix the bug. According to Microsoft, we should expect to see similar fixes for Access 2010, 2013, and Office 365 (the Click-to-Run version 1911) this Friday, Nov. 22. The fix for Office 365 Semi-Annual channel (version 1901) is due next Monday, and Volume Licensees won\u2019t get the bug erased until Dec. 10. Which is why you pay for a Volume License, right?<\/span><\/p>\n

G\u00fcnter Born <\/span>also reports<\/span><\/a> that Access 2016 Click-to-Run has already been fixed, with build 12130.20390, according to a German-language post.\u00a0<\/span><\/p>\n

Stuck with Access? Join us <\/span>on AskWoody<\/span><\/a>.<\/span><\/em><\/p>\n

http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Tue, 19 Nov 2019 06:09:00 -0800<\/strong><\/p>\n

\n
\n

Although we\u2019ve been promised no \u201cC\u201d or \u201cD\u201d week second cumulative updates for the rest of the year \u2014\u00a0<\/span>at least for Windows<\/span><\/a>\u00a0\u2014 Microsoft has acknowledged a bug it created in last week\u2019s Patch Tuesday Office patches, and now promises that it\u2019ll update the bad fixes on most machines this week or next. Those are “C” week and “D” week, respectively.<\/span><\/p>\n

The cause du jour: a bug in all of this month\u2019s Office security patches that throws an error in Access saying, \u201cQuery xxxx is corrupt,\u201d when in fact the query in question is just fine. Microsoft describes the erroneous error message on its<\/span> Office Support site<\/span><\/a>:<\/span><\/p>\n

To read this article in full, please click here<\/a><\/p>\n<\/section>\n<\/article>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[11062,10643],"tags":[10516,714,10525],"class_list":["post-16924","post","type-post","status-publish","format-standard","hentry","category-computerworld","category-independent","tag-microsoft","tag-security","tag-windows"],"_links":{"self":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/16924","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=16924"}],"version-history":[{"count":0,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/16924\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=16924"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=16924"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=16924"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}