Blog Post

Access Blog
2 MIN READ

Access Releases 7 Issue Fixes in Version 2311 (Released November 25th, 2023)

lindalu-MSFT's avatar
lindalu-MSFT
Icon for Microsoft rankMicrosoft
Dec 17, 2023

Our newest round of Access bug fixes was released on November 25th, 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 Version 2311, you should have these fixes. Make sure you are on Access Build # 16.0.17029.20068 or greater. 

 

Bug Name 

Issue Fixed  

Reserved error -1001 when using a reserved word in a SQL query 

This would only happen if the option to use “SQL Server Compatible Syntax (ANSI 92)” was enabled. In that case the use of a reserved word for a table or field name would generate this error. We will no longer generate an error if Access does not use the specific reserved word, and it will allow the word to be used as a name, without error. 

Report in report view shows navigation controls 

The record navigation controls that appear at the bottom of a form window that allow you to move to first/last records, etc. should never appear for a report in report view. The “Navigation Records” property is not exposed for reports, but if the “Scroll Bars” property was set from VBA while a report was open in report view, the navigation controls would incorrectly be displayed. 

Can’t open a query directly into SQL view 

Previously to get to SQL view, you’d have to open in query design view first, then switch to SQL view, now you can open directly into SQL view, using a context menu, or code/macro. 

Navigation Pane does not display text correctly when collapsed 

When the Navigation Pane is collapsed, it should read “Navigation Pane” with the text oriented counter-clockwise 90 degrees, but instead the text was being garbled. 

When you navigate using the new Edge browser control using the Navigate method while the control is hidden, then set the Visible property to True, the control does not show the correct page 

The control now performs the navigation when it is made visible. 

In some cases, using an append query with a linked Dataverse table could cause Access to terminate 

This scenario will no longer encounter an issue. 

Applying multiple filters to a linked Dataverse table could cause Access to terminate 

Applying a filter to a linked Dataverse table could ‘leak’ open tables, and eventually cause Access to terminate, this issue is now fixed. 

 

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

 

Updated Aug 13, 2025
Version 2.0
access
bug fixes
Dataverse
developer
edge browser
office 365

29 Comments

Sort By
Show More
  • NeilSargent's avatar
    NeilSargent
    Copper Contributor
    Dec 24, 2023

    Colin,

     

    The trouble is V2311 is still the current release (current channel). So even if it is fixed on the insider programme, my clients will have to wait.

     

    For now, I have had to disable the browsing function and remove the bad control from the application. The first time I saw it, it could have been due to Windows 11/10. Then a second client's app died and I suspected V2311. Then my own development PC updated to V2311 and it also died.

     

    It would have been nice to have had the release notes on time to have been able to substantiate my hypotheses that is was a bug in MS365 and not my application. It would also have saved me several hours of debugging. A three week delay is simply not acceptable.

     

    My application is way too complicated to be used as a demo, but I did manage to distil the problem down to the nested event procedure behaviour I describe. Do you need me to provide a demo database exhibiting the problem? It will have to wait for the New Year though.

  • NeilSargent's avatar
    NeilSargent
    Copper Contributor
    Dec 24, 2023

    It really is important to release these notes earlier. Over the last two weeks I have had two different client applications crashing whenever a form containing the Edge Browser control was opened. It coincided with the release of office V2311 but the official release notes did not list any Access changes and had no mention of the Edge Browser control.

     

    I have managed to isolate the problem to the following:

     

    If a form does something with its recordset in the Open or Load event handlers, it is forced to do a sort of "double-load". This allows it to completely load in the background during the initial Load event so that it may complete the recordset operation. It then proceeds to run the later event handlers. This behaviour can be observed by multiple occurrences of the form's Current event and events within any subforms, first during the premature load invoked by the Load event, and then again when the Load event has completed and it there own turn to run.

     

    If the form with this behaviour contains the modern web browser control and the version is V2311, Access crashes. The web control does not need any code, merely its presence causes the crash.

     

     

  • isladogs's avatar
    isladogs
    MVP
    Dec 19, 2023

    Many thanks for all of these fixes, four of which I recognise as I reported them recently and all affect me directly.

    1. I will update my article on reserved errors to mention the -1001 fix for reserved words in SQL View queries.

    2. As you already know I'm very grateful for being finally able to open queries directly into SQL view. I'm now just waiting for that feature to be added to the Create ribbon as well

    3. The recent fix to the Edge browser control bug was also very welcome

    4. I'd also just like to mention the very prompt fix to the recent font display bug. Reported on a Friday evening & fixed the following Monday. That was very impressive!

     

  • Shane Groff's avatar
    Shane Groff
    Icon for Microsoft rankMicrosoft
    Dec 19, 2023

    Yes, that's because it picks the first event in the list (AfterUpdate).  If you choose Build Event from the context menu in form design, it will select the control with the DocumentComplete event selected, which won't crash, since it is supported.

     

    Shane

  • RichardRost's avatar
    RichardRost
    MVP
    Dec 18, 2023

    Hi Shane. Thanks for replying. The browser control will crash Access immediately if you add it as a control on a new form and go right to the VB editor and pick the control from the list. Easier to show you: Edge Control Crashing Access

     

    Let me know if you have any questions or need any more info from me.

     

    RR

  • Shane Groff's avatar
    Shane Groff
    Icon for Microsoft rankMicrosoft
    Dec 18, 2023

    Hi Richard,

     

    I think you will find that if you choose an event (such as KeyDown) that is supported by the Edge Browser control, then it will not crash.  If you choose an event that is not supported by the control, then it will crash.


    We will definitely fix this (the events that are not supported should not appear in the list, but even if they were there for some reason, it should not cause a crash).

    Look for this fix for this in an upcoming bug blog.

     

    Thanks for the report.

     

    Shane

  • RichardRost's avatar
    RichardRost
    MVP
    Dec 17, 2023

    Thank you for this. Not sure if it's been reported to the team yet or not I'm sure it has I probably just haven't seen it but I'm experiencing an issue where if I am working with the new Edge browser control and I go into the Visual Basic editor if I select the browser control from the drop-down on the left and any of the events from the drop-down on the right then Access crashes and it happens every time on multiple machines.