This set of fixes covers two versions, so all fixes are available in version 2402, which was released on February 28th, 2024. 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 2402, you should have these fixes. Make sure you are on Access Build # 16.0.17328.20142 or greater.
|
Bug Name |
Issue Fixed |
|
Autocomplete for a Combo Box control may not work if the dropdown displays numbers and there are negative numbers in the list |
Autocomplete will now work properly when there are negative numbers in the dropdown list. This also prevents the “Not in List” event from firing when the item is in the list. |
|
If the default value of a field is an asterisk (*) or other binary operator, and is not surrounded by quotes, an error will be generated. |
The error displayed would be "Syntax error (missing operator) in table-level validation expression." |
|
When you set the Visible property of an Edge browser control to true (if it was previously false), the control does not navigate to its URL |
Now when an Edge browser control is made visible, it will display the correct URL based on any navigation that has occurred. |
|
Trying to use the Navigate method on a hidden Edge browser control could cause Access to terminate unexpectedly. |
This will now work safely. |
|
If a form has a hidden Edge control and the Record Source property of the form is modified in the form’s Open event, Access may terminate unexpectedly. |
Actions that cause the form to repopulate its data will no longer cause issues when there are hidden Edge browser controls on the form. |
|
The tool gallery in form layout view does not show the new Edge browser control |
The tool gallery in form layout view shows a subset of the controls displayed in form design view. The new Edge browser control will now appear in the layout view tool gallery. |
|
Choosing an event from the event dropdown for the Edge browser control in the VBA (Visual Basic for Applications) IDE (integrated development environment) that is not supported can cause Access to terminate unexpectedly |
All events in the VBA IDE can now be safely selected. |
|
Cannot navigate to local file if edge browser is initially blank |
The Edge browser control prevents navigation from a web location to a local file. If no initial value was specified in the control source property of an Edge browser control, then the ‘about:blank’ page was considered to be a web location, and navigation to a local file was blocked. This navigation will now be allowed. |
|
Setting control source of Edge control in form view does not cause control to navigate |
When the control source property for an Edge browser control is set using VBA code while a form is in form view, the browser control will now update to display the correct page. |
Please continue to let us know if this is helpful and share any feedback you have.
Microsoft
