Access Blog:
Here's a summary of bug fixes available in the latest Current Channel build of Access. Please comment if you still see any of the following issues.
Bug Name | Issue Fixed |
|---|---|
| Edge Browser Control didn't render PDFs on some machines | When the Edge Browser Control was used to display a PDF, on some machines the PDF would not render at all if the registry value "HKEY_CLASSES_ROOT\.pdf\Content Type" was missing. Access now provides the missing content type, so the Edge Browser Control can render the PDF. |
| Export to SharePoint failed for tables with both lookup fields and attachment columns | When exporting an Access table to a SharePoint list, if the table contained both a lookup field and an attachment column, the export could fail with an error. The export now handles this combination correctly, so the export completes successfully. |
| Conditional Formatting color picker showed a reduced palette in Version 2604 | A regression introduced in Version 2604 caused the Conditional Formatting color picker to display a smaller set of color choices than previous versions. The full legacy color palette has been restored. |
| Some Unicode characters displayed incorrectly in objects exported to Excel | When exporting an Access object whose name contained certain extended Unicode characters, the resulting file's sheet name displayed the characters incorrectly. These characters are now preserved correctly during export. |
| Power BI Gateway couldn't refresh semantic models from .accdb files | Refreshing a Power BI semantic model that connected to a .accdb file via the on-premises gateway could fail with "Unspecified error". Connection setup has been adjusted so the gateway can successfully refresh the model. |
| Monaco SQL view: Ctrl+Z didn't undo Ctrl+Shift+K line deletion | In the new Monaco-based SQL editor, pressing Ctrl+Shift+K to delete the current line removed the line, but a subsequent Ctrl+Z would not restore it. Undo now works correctly for this and similar editing operations. |
| Document tab text didn't scale with Windows text-size setting | When the Windows display setting for text size was increased, document tab labels and the record navigation bar continued to render at the standard size, while other Access UI scaled correctly. The document tabs and record navigation bar now honor the system text-size setting. |
| Error when editing a Long Text field after a write conflict | When a write conflict occurred on a record containing a Long Text field, subsequent attempts to edit the field could fail with an error. The data path now refreshes the cached field values correctly after a conflict so that further edits succeed. |
| Access terminated unexpectedly when reading Edge Browser Control properties in form design view | In form design view, retrieving the ReadyState or LocationUrl property on an Edge Browser Control could cause Access to terminate unexpectedly. Both properties now return safely in design view. |
| "Copy" prefix was prepended instead of appended to copied object names | When duplicating a database object, Access named the copy "Copy of Form1" instead of "Form1 - Copy". This made copies of related objects sort apart from their originals in the Navigation Pane. Copy-of names now append the suffix, so related objects stay together when sorted alphabetically. |
Source:
Bug fixes in Microsoft Access - Current Channel Version 2605 (Build 16.0.20026.20118) | Microsoft Community Hub
Bug Name Issue Fixed Edge Browser Control didn't render PDFs on some machines When the Edge Browser Control was used to display a PDF, on some machines...
techcommunity.microsoft.com
