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 2404, you should have these fixes. Make sure you are on Access Build # 16.0.17531.20120 or greater.
|
Bug Name |
Issue Fixed |
|
Characters in the extended range of support not correctly exported to HTML |
When exporting data to HTML, some characters would not be represented properly when the HTML file was viewed, and would display as question marks or boxes |
|
Characters in the extended range of support not correctly displayed in charts |
When creating a chart with data that contained characters from the extended range of support, some characters would not be represented properly and would display as question marks or boxes |
|
Data appears incorrect when exporting tables with multiple relationships |
Dataverse does not support multiple relationships between two tables, so we now alert you when attempting to export such tables and give some options to safely proceed |
|
Application.Run would not execute code when Macro Settings require signed macros, even if the target database is signed |
If Application.Run executes code from an external database, we now validate the signature on the external database, and allow the code to run if the database is signed.
|
|
An error may occur when trying to filter for a selection |
When selecting a substring in a field, and then choosing to filter for values that contain the selected string, you could get an error that you used an invalid expression.
|
|
Slow performance when executing query against linked SQL Server table that restricts on Large Number field |
In general, when a query applies a restriction to a linked SQL Server table, SQL Server performs the restriction, so only the filtered data is returned to Access. This was not being done for Large Number fields, so the entire table was being downloaded, then filtered locally. |
|
Access terminates unexpectedly when using right-click on a macro or query in the Navigation Pane |
Access will now handle this correctly in all cases |
Microsoft
