Our newest round of Access bug fixes was released on June 26th, 2023. In this blog post, we highlight 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 are on the current monthly channel build 2306, you should have these fixes. Make sure you are on Access Build # 16.0.16529.20154 or greater.
|
Bug Name
|
Issue Fixed
|
|
Performance degradation when using ADODB to manipulate data from Excel VBA
|
To support the use of OLEDB interfaces by applications other than Office applications when using the Access Database Engine in a Click-to-Run installation, there is some overhead necessary. That overhead was impacting use of the Access Database Engine from Excel as well, but now the overhead has been removed in that case.
|
|
DLookup doesn't work properly if a TempVar, or other object is specified as the Criteria argument
|
The Criteria parameter accepts a Variant, so an object can be supplied, but the call to DLookup requires a String. If an object is supplied, then Access needs to get the default property value from the object to convert to a string. Without this change, Access ignored the Criteria argument, and treated the expression as if no Criteria was supplied.
|
|
The Edge Browser Control does not display local files if they have non-Ansi characters in the name
|
The Edge Browser Control can display local files of the appropriate type, but this functionality was not working if the filename contained characters outside the Ansi range.
|
|
During Dataverse Export, there is little feedback
|
The Dataverse progress indicator will now show each table name as it is exported, and additional processing steps.
|
|
Out of memory error when opening a report
|
When the Application Icon option for the database was set, and a form was opened before the first report was opened, the out of memory error was generated. This is fixed.
|
|
Multiple accessibility issues with the Contacts template
|
Focus indicator around some buttons not visible.
Tab order in Contract Details is not logical.
The tab key does not cycle through controls in Contact List header.
The contrast between some text and the background in the Contact Details form is insufficient.
|
Please continue to let us know if this is helpful and share any feedback you have.
