Blog Post

Access Blog
2 MIN READ

Access Releases 6 Issue Fixes in Version 2306 (Released June 26th, 2023)

lindalu-MSFT's avatar
lindalu-MSFT
Icon for Microsoft rankMicrosoft
Jul 05, 2023

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.  

 

 

Updated Nov 09, 2023
Version 2.0
  • Hi Mohsin,

     

    The issue with loading files from network locations will be fixed in Version 2308.

     

    For the second issue regarding getting the message "There isn't enough memory...", there is a known issue that when switching themes with a datasheet open, you may see this error, which will be fixed in an up-coming version.  However, I have not been able to reproduce this otherwise.  Is this issue specific to a particular table/form, or happening in all cases?  Is it possible users changed themes?

     

    Shane

  • abcwork's avatar
    abcwork
    Copper Contributor

    Hi lindalu-MSFT ,

     

    Thank you for the updates, I am writing to report two bugs that I have found in version 2306.

     

    • The first bug is that the Edge browser control has stopped working with dealing with paths on network locations. This bug was not present last week, but it is now occurring in both the current channel and the insiders' build. Please see the following cross posting link (https://www.access-programmers.co.uk/forums/threads/microsoft-access-edge-browser-control-is-finally-here.326988/post-1881643) on the forum for more details..
    • The second bug is that current channel users are receiving the error message "There isn't enough free memory to update the display. Close unnecessary programs and try again." This error message specifically occurs when a datasheet form has a Subdatasheet form associated with it. To reproduce the error, you may need to open or collapse the Subdatasheet form. Once the error message appears, the entire datasheet will start flickering.

       

    I would appreciate it if you could look into these bugs and let me know if there are any workarounds or if a fix is in the works.

     

    Please let me know if you need any further details.

     

    Thank you for your time.

    Sincerely,

    Mohsin