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.    ...
Updated Aug 13, 2025
Version 2.0
access
bug fixes
Dataverse
developer
edge browser
office 365
NeilSargent's avatar
NeilSargent
Copper Contributor
Jan 09, 2024

Thank you Karl.

 

I have managed to workaround the crashing for V2311 and V2312 by setting the control's Visible property to True but hiding it by setting its Height and Width properties to zero.

 

Incidentally, the problem also exists if the control's Visible property is set to True but the control is on a tab control page which is not visible.

 

However my application uses an unbound web browser control as a local file browser on a bound form. It will browse local files if you navigate to a local file in the Form_Load event. I have found that any subsequent change to the form's Filter property "resets" the browser control. It navigates to about:blank and will no longer then browse any local files (instead it raises a NavigateError event with StatusCode 10).

 

Setting the ControlSource to a local file appears to solve this "reset" problem. However AFAIK there is no way to set the ControlSource at runtime and no way to know the path to a local file at design time.