{"id":25648,"date":"2022-07-14T00:15:00","date_gmt":"2022-07-13T22:15:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=25648"},"modified":"2022-07-19T15:43:03","modified_gmt":"2022-07-19T13:43:03","slug":"office-updates-destroys-access-run-time-and-apps","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2022\/07\/14\/office-updates-destroys-access-run-time-and-apps\/","title":{"rendered":"Office updates destroys Access run time and apps"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2012\/07\/Office1.jpg\" width=\"55\" height=\"60\" align=\"left\" \/>[<a href=\"https:\/\/www.borncity.com\/blog\/2022\/07\/12\/zerschiet-office-version-2206-build-15330-20246-access-bibliotheken\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]I got reports, that Microsoft Office 365 version 2206 (Build 15330.20246) is causing issues with VBA in Access applications. And I got reports, that KB5002121 for Office 2013 and KB5002112 for Office 2016 is causing the same issue.<\/p>\n<p><!--more--><\/p>\n<h2>1# Report on Office 365 issues<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg04.met.vgwort.de\/na\/309ff646e9df4aac9dd43221fd84d1f2\" alt=\"\" width=\"1\" height=\"1\" \/>The first report I received via Twitter. The person in question thinks that Microsoft has once again ruined Access with an Office update and posted the following screenshot of the error message in a <a href=\"https:\/\/twitter.com\/tmigge\/status\/1546842905544998913\" target=\"_blank\" rel=\"noopener\">tweet<\/a> &#8211; the German text means translated:<\/p>\n<p><a href=\"https:\/\/twitter.com\/tmigge\/status\/1546842905544998913\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" title=\"Access-Fehler\" src=\"https:\/\/i.imgur.com\/wOMwQuZ.png\" alt=\"Access-Fehler\" \/><\/a><\/p>\n<blockquote><p>You have entered the expression On Load as the event property setting. This expression has caused an error: Requested class library or wizard is not a VBA project.<\/p><\/blockquote>\n<p>If you search for the bug, there are quite a few hits &#8211; and a <a href=\"https:\/\/docs.microsoft.com\/en-us\/office\/vba\/language\/reference\/user-interface-help\/requested-type-library-or-wizard-is-not-a-vba-project\" target=\"_blank\" rel=\"noopener\">support post<\/a> from April 2022. From the post, I conclude that there was either a reference to a library disabled (you can find out in the VBA environment) or a reference broken by the update. Anyone else who happens to have this bug and can elaborate? The user replied on Twitter:<\/p>\n<blockquote><p>The error occurs with our customers who have installed update 15330.20246. It disappears when you revert to 15330.20230 OR create a new ACCDE with the newer Access version. This will then run on both builds, but not on older Office versions. By this I mean Access 2013 or 2010.<\/p><\/blockquote>\n<p>So it seems to be related to the latest update. However, the user also points out that build 15330.20246 is not yet listed in the <a href=\"https:\/\/docs.microsoft.com\/en-us\/officeupdates\/update-history-microsoft365-apps-by-date\" target=\"_blank\" rel=\"noopener\">Microsoft 365 update history<\/a>. At this point, my thanks to the reader for the information.<\/p>\n<h2>#2 Report on Access Run Time issues<\/h2>\n<p>A short time later I received the notification within the following <a href=\"https:\/\/twitter.com\/KVEntwicklung\/status\/1547165438735433728\" target=\"_blank\" rel=\"noopener\">tweet<\/a>, that an installed Access Run Time (RT) also seems to show these errors.<\/p>\n<p><a href=\"https:\/\/twitter.com\/KVEntwicklung\/status\/1547165438735433728\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" title=\"Run Time Error with Access Run Time\" src=\"https:\/\/i.imgur.com\/bs6nTym.png\" alt=\"Run Time Error with Access Run Time\" \/><\/a><\/p>\n<h2>#3 Report Office 2013\/2016 also affected<\/h2>\n<p>In another <a href=\"https:\/\/twitter.com\/tmigge\/status\/1547216272168976386\" target=\"_blank\" rel=\"noopener\">tweet<\/a>, the first user reported, that the error occurs after installing Office 2013 update <a href=\"https:\/\/support.microsoft.com\/en-gb\/topic\/description-of-the-security-update-for-office-2013-july-12-2022-kb5002121-0fbb672a-ae65-4646-a059-0c3e83edc458\" target=\"_blank\" rel=\"noopener\">KB5002121<\/a> or Office 2016 update <a href=\"https:\/\/support.microsoft.com\/en-gb\/topic\/description-of-the-security-update-for-office-2016-july-12-2022-kb5002112-214149c3-42cc-4012-b408-1c8e7c0b2f3e\" target=\"_blank\" rel=\"noopener\">KB5002112<\/a>. In all cases, the Access error in Run Time or in Access apps accessing ACCDE files has been gone, after the update install has been rolled back.<\/p>\n<p><strong>Addendum:<\/strong> <a href=\"https:\/\/answers.microsoft.com\/en-us\/msoffice\/forum\/all\/kb5002121-breaks-ms-access-runtime-applications\/dc708b2e-0307-4edc-9268-e1eaaa83b660\" target=\"_blank\" rel=\"noopener\">Microsoft says<\/a>, they are aware and the team is looking into that issue (some affected German blog reader had created tickets). On reddit.com there is <a href=\"https:\/\/www.reddit.com\/r\/MSAccess\/comments\/vy5wtr\/issues_with_kb5002112kb5002121_vbe7dll\/\" target=\"_blank\" rel=\"noopener\">this thread<\/a> about that issue.<\/p>\n<p><strong>Addendum 1:<\/strong> See\u00a0<a href=\"https:\/\/borncity.com\/win\/2022\/07\/19\/fix-for-access-accde-mde-bug-vba-library-bug\/\" rel=\"bookmark\">Fix for Access ACCDE\/MDE bug (VBA library bug)<\/a> for fixes.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]I got reports, that Microsoft Office 365 version 2206 (Build 15330.20246) is causing issues with VBA in Access applications. And I got reports, that KB5002121 for Office 2013 and KB5002112 for Office 2016 is causing the same issue.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,11,22],"tags":[1782,47,195],"class_list":["post-25648","post","type-post","status-publish","format-standard","hentry","category-issue","category-office","category-update","tag-access","tag-issue","tag-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/25648","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=25648"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/25648\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=25648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=25648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=25648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}