| First Published 31 Mar 2026 | Last Updated 6 Apr 2026 |
|---|
This article provides information about Access bugs, issues and fixes reported during March 2026 (in order of date reported) including symptoms and action taken.
I am only aware of one new issue this month and this has already been fixed in insider channels along with many other fixes to older bugs.
IMPORTANT:
Insider channels (particularly Beta Channel) are used by Microsoft to test new features before these go to production channels.
It is to be expected that the insider channels may contain bugs. These channels should only be used for testing purposes and NEVER for production use.
However, it is also the case that insider channels are often the first to receive fixes to older bugs. This article includes a long list of fixes released in the beta channel this month.
Newly reported bugs
| Item | Bug information | Date Reported | Reported By | Action taken |
|---|---|---|---|---|
| a) | Problems opening reports for some users in Current Channel (Preview) Version 2603 In some cases, Access crashed when opening a report. Other users reported error 438: Object Doesn't Support this Property or Method. | 2026-03-16 | Karl Donaubauer | Fixed in Current Channel Preview version 2603 19822.20086 (2026-03-18) Also fixed in Beta channel version 2604 19916.20000 (2026-03-19) |
Related Articles:
a) Thread in German forum: Problem Office Update Version 2603 Build 19822.20044
Possibly related post at Access World Forums: Open report in VBA not working after windows 11 update
Bug fixes in Current Channel Version 2603 Build 19822.20114 (released 2026-03-24)
The Access team have published a blog article listing the following ten Access fixes released in Version 2603 (Build 19822.20114)
| Item | Bug information | Issue Fixed | Related Articles |
|---|---|---|---|
| a) | Edge Browser Control didn't navigate from code when inside a tab control | When the Edge Browser control was hosted in a tab control, calls to the Navigate method from VBA succeeded, but the control didn’t refresh to show the new page. Switching tabs forced the refresh. The control now refreshes automatically after navigation, even when it’s hosted in a tab control. | |
| b) | Some Unicode characters displayed incorrectly in Quick Import | Certain extended Unicode characters were displayed as squares when importing data using Quick Import. These characters are now displayed correctly. | |
| c) | Modern Chart titles truncated in Print Preview | When viewing a report containing Modern Charts in Print Preview, chart titles might be truncated. Chart titles now render correctly in Print Preview. | Modern Chart Improvements: Part 1 See Issues item g)Access Bug / Issues Summary - Nov 2025 See item a) |
| d) | Some Unicode characters displayed incorrectly in exported object names | When exporting an object whose name contained certain extended Unicode characters, the sheet name in the exported file displayed the characters incorrectly. These characters are now preserved correctly during export. | |
| e) | Some Unicode characters displayed incorrectly in error messages for long object names | When renaming a database object to a name that was too long, the error message displayed certain extended Unicode characters incorrectly. These characters now display correctly in error messages. | |
| f) | Standard colors in Access didn't match other Office apps | The standard color palette in Access used different color values than other Office applications like Word and Excel. For example, the standard red in Access was #ED1C24 instead of the updated Office standard red #EE0000. The color palette has been updated to match the rest of Office. | Microsoft Access rolls out new Office default theme and font |
| g) | Field.Properties("Precision") and Properties("Scale") on a query column caused the query to execute | Accessing the Precision or Scale properties of a field in a query's Fields collection caused the query to execute. This was a regression that broke add-ins and code that enumerate field properties, since query execution can be expensive and have side effects. These properties are now returned without executing the query. | |
| h) | Toggle filter button in status bar didn't work when no records were displayed | When a form filter resulted in no matching records, clicking the Toggle Filter button in the status bar to remove the filter had no effect. The button now properly removes the filter even when the filtered result set is empty. | See Item a) |
| i) | PDF files with capitalized extension didn't render in Edge Browser Control | When navigating to a PDF file using the Edge Browser control, if the file extension was capitalized (e.g., ".PDF" instead of ".pdf"), the file contents were rendered as raw text instead of as a formatted PDF document. The extension comparison is now case-insensitive. | |
| j) | Monaco SQL editor inserted blank lines in multi-line comments | When switching between Design View and SQL View, the Monaco SQL editor inserted blank lines between each line inside /* multi-line comment */ blocks. This affected both local and passthrough queries. The editor now preserves the original comment formatting. | See Fixed Issues 32) |
Bug fixes in Beta Channel Version 2604 Build 19923.20002 (released 2026-03-26)
The information below was kindly provided by a member of the Access team with related articles added by me. Most of the fixes listed below are currently only available in the Beta Channel but should roll out to other channels in the coming months.
| Item | Bug information | Issue Fixed | Related Articles |
|---|---|---|---|
| a) | Datasheet displays incorrect record when simultaneous entries are submitted to SQL Server | When multiple records were submitted simultaneously to a SQL Server-linked table, the datasheet could display the wrong record after saving. The datasheet now correctly refreshes to show the intended record. | |
| b) | Values display in the wrong control when using a form as a sublist | When a form was used as a sublist (subdatasheet), field values could display in the wrong control, showing data in incorrect positions. Values now display in the correct controls. | |
| c) | Applications that use the Access Database Engine (ACEOLEDB) terminate unexpectedly on exit | Third-party applications using the Access Database Engine (ACEOLEDB) provider could terminate unexpectedly when closing. The shutdown sequence has been corrected. | |
| d) | Long Text field corrupted when a query updates a record while a user is editing it | When a query updated a Long Text field on a record that was simultaneously open for editing, the field data could become corrupted. The record update now correctly handles concurrent access to Long Text fields. | |
| e) | Rendering errors with Aptos (Detail) font | Controls using the Aptos (Detail) font variant could render incorrectly, with characters appearing misaligned or garbled. The font rendering has been corrected. | See Item c) |
| f) | Standard colors in Access didn't match other Office apps | The standard color palette in Access used different color values than other Office applications like Word and Excel. The color palette has been updated to match the rest of Office. |
Microsoft Access rolls out new Office default theme and font |
| g) | Option Group with Vertical Anchor Bottom: option buttons show incorrect visual state after clicking | When an option group control had its Vertical Anchor property set to Bottom, clicking an option button would not correctly update the visual state of the buttons. The visual state now updates correctly regardless of the anchor setting. | See Item b) |
| h) | SQL View: Ctrl+K should toggle pretty formatting off/on | In the Monaco SQL editor, the Ctrl+K keyboard shortcut did not toggle SQL formatting. Ctrl+K now correctly toggles pretty formatting on and off. | See Item 4: Pretty formatting of SQL |
| i) | Monaco editor incorrectly converts Unicode characters in SQL view | When switching between Design View and SQL View, the Monaco SQL editor could incorrectly convert certain Unicode characters, corrupting the SQL text. Unicode characters are now preserved correctly. | See Known Issues d) |
| j) | Importing text files with Unicode characters in the filename fails | Attempting to import a text file whose filename contained certain Unicode characters would fail. File imports now handle Unicode filenames correctly. | |
| k) | Added VarP and StDevP to the Totals query aggregate dropdown | The VarP (population variance) and StDevP (population standard deviation) aggregate functions were missing from the Totals row dropdown in Query Design view. They have been added alongside the existing Var and StDev options. | |
| l) | Added VarP and StDevP to the datasheet totals row dropdown | The VarP and StDevP aggregate functions were missing from the Totals row dropdown in Datasheet view. They have been added to match the options available in Query Design view. | |
| m) | Access hangs at shutdown when VBA holds temporary DAO field references | Access could hang during shutdown when VBA code created temporary DAO field references. The shutdown process now correctly cleans up temporary field references. | |
| n) | Full Screen Mode ribbon display option does nothing in Access | Selecting "Full Screen Mode" from the ribbon display options had no effect in Access. This option now works correctly, hiding the ribbon to maximize the available workspace. |
Feedback
Please use the EMail button in the contact form below to let me know whether you found this article interesting/useful or if you have any questions/comments.
Please also consider making a donation towards the costs of maintaining this website. Thank you
| Colin Riddington | Mendip Data Systems | Last Updated 6 Apr 2026 |
|---|
|
Return to Bugs & Fixes Page
|
Return to Top
|