Our newest round of Access bug fixes was released on December 6th. 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’re on the current monthly channel version 2211, you should have these fixes. Make sure you are on Access Build # 16.0.15831.20190 or greater.
|
Bug Name
|
Issue Fixed
|
|
Decimal field with percentage formatting loses format when clicked on
|
When editing a field with formatting (such as a Percentage format), Access typically retains the formatting while editing. This was not working properly for Decimal fields. The formatting was removed when a field with a Decimal value was clicked on, making it more difficult to visualize the edited value. Access now retains formatting when editing Decimal values.
|
|
Form On Load event runs during Access shutdown
|
The On Load event for a form should run once—when the form opens. In some cases, the On Load event runs again during the process of closing the Access application, which closes all open objects. Access now runs the On Load event only once when the form is opened.
|
|
When validating data for exporting to Dataverse, the query indicating issues includes columns that have no issues
|
When exporting an Access table to Dataverse, Access identifies issues that may cause a problem during the process and generates a query identifying rows and columns in the table that may need to be fixed before a successful export can occur. This query now does not include columns that have no issues that prevent the table from successfully exporting to Dataverse.
|
|
Text is not visible in the Find and Replace dialog in SQL View when Office Theme is set to black
|
When the Office Theme was set to black, the Find and Replace dialog color was not correctly updated to provide proper contrast with the dark background. The text color is now updated appropriately and has the correct contrast.
|
|
Access becomes unresponsive when dropping the column menu for a large table
|
Each column in a datasheet has a menu to display options for sorting and filtering using values in the column. Previously, in a large table, Access ceased to react to user input when this menu was selected. Access now responds appropriately when this menu is used, regardless of the size of the table.
|
|
Screen reader does not read all columns in the selected row of a Combo Box list
|
When using a screen reader (Narrator, NVDA, JAWS, etc.) and the list for a Combo Box is expanded, screen reader should read the value for the selected row. Previously, if the list displayed multiple columns, the screen reader announced the value in the first column only. Now, the screen reader announces all columns of the selected row.
|
|
Field with Conditional formatting, and Can Grow set to Yes not expanding to show all lines of text when printing
|
When the Can Grow property of a Textbox is set to Yes, Access increases the height of the Textbox when printing to display all the text in the field. Conditional formatting was not considered when calculating the size of the text. If conditional formatting was applied, and affected the size of the text (e.g., by applying the Bold format), Access left insufficient space for the text. Access now properly accounts for conditional formatting when determining the space necessary for the text.
|
|
Field with Border Style set to Transparent, and Can Grow set to Yes not expanding to show all lines of text when printing
|
When the Can Grow property of a Textbox is set to Yes, Access increases the height of the Textbox when printing to display all the text in the field. The calculation of the necessary space was not correct if the field used transparent borders leading to insufficient space being provided. The calculation is now fixed for transparent borders so all text will be displayed.
|
Please continue to let us know if this is helpful and share any feedback you have.
