Access Releases 6 Issue Fixes in Version 2209 (Released September 26)

Posted by

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Community Hub.

Our newest round of Access bug fixes was released on September 26. In this blog post, we are highlighting some of the fixed issues that our Access engineers released in the current monthly channel.   

If you see a bug that impacts you, and if you’re on the current monthly channel build 2209, you should have these fixes. Make sure you are on Access Build # 16.0.15629.20156 or greater. 


Bug Name 

Issue Fixed  

Access Database Engine fails to load when used as a Data Access Objects (DAO) provider 


When using DAO from an application other than a Microsoft 365 app (e.g., a custom application written in C#/C++/VBScript) you may get an error: "The operating system is not presently configured to run this application."  This update fixes the issue. 

Visual Basic for Applications (VBA) performance regression in Excel when looping through DAO Recordset 


When looping through a DAO Recordset in VBA code in an Excel macro, the code runs significantly slower than previously. This update restores performance to previous levels. 

No error shown when trying to open unsigned macro in .mdb or .mde file 


If the Trust Center Macro Settings option is set to "Disable all macros except digitally signed macros", Access blocks opening any database that isn't signed with a code signing certificate. This update adds an error message to indicate the reason that the database won’t open when a user attempts to open a database without a signature. Previously, there was no indication why the database was blocked from opening. 

Access terminates unexpectedly when using aggregate functions in query 



When executing a query that doesn’t select from any table, and using an aggregate function, e.g., "Select Sum(5)", Access terminates unexpectedly. This update prevents this from happening, and causes #Error to display when the query is executed. 


Using the Access Database Engine as an OLEDB provider (Microsoft.Ace.OLEDB.16.0) to connect to an Access database with links to SharePoint lists may cause an application to terminate unexpectedly 

This update fixes an issue that could cause the application to terminate unexpectedly when using the Access Database Engine OLEDB API with a database containing links to SharePoint lists. 

Additional details for saving import/export specs no longer appear 

When exporting a table to an external data source (Excel, text, etc.), there is an option to Save Import/Export steps. If you check this option, you should be provided with the ability to specify a name/description for the saved operation. 

This update fixes an issue that prevents the options to enter this data from showing in the wizard. 


Please continue to let us know if this is helpful and share any feedback you have. 

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.