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!
