Access fixes released in Version 2604 (Build 16.0.19929.20090)
Bug Name Issue Fixed 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. 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. 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. 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. 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. 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. Query Design: Insert/Delete Columns don't work when ribbon is set to Show Tabs Only In Query Design view, the Insert Columns and Delete Columns commands on the ribbon did not work when the ribbon display option was set to "Show Tabs Only." The commands now work correctly regardless of ribbon display mode. 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. 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. 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. 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. 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. 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. 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.
ODBC error (incorrect syntax) since 2604
Overnight i have the problem that many inserts in my MS Access app do not work anymore. I get the error Run-time error '3155': ODBC--insert on a linked table 'tablename' failed. [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '='.(#102) I have been able to isolate this issue on a column of type NVARCHAR(MAX). If I insert any value except null in this column the error above will show on save. I tested with other variants of NVARCHAR. The problem happens starting from NVARCHAR(256), thus what is Long Text for Ms Access. When i insert the record first with a value null for this column, no error is generated and the record is saved. If i 'Update' the record later with a text value in this column, that is no problem. So, the ODBC connection generates a sql insert statement that is mallformed in case of a long text. I have this problem consistent on all apps and all tables where i have NVARCHAR(>255). My solution is to go back to office release 2508 (semi annual support).
Microsoft Access and Outlook
Hi there, I have just updated my laptop (with a view for a faster laptop!) However, Access was working fine and now i can't send emails from access through outlook like before. I get a message to say a program is trying to send an email message on your behalf. I'm not sure how to get rid of this warning! Please help.... Thank you in advanceAccess announces retirement of Database Compare tool in June 2026
MS Access currently ships a standalone Database Compare tool (DATABASECOMPARE.EXE) that enables comparison of two Access databases. As of June 2026, this tool will no longer be distributed and installed with Office. Access is retiring the Database Compare tool because it depends on components that are no longer available and fails to launch reliably on many Office installs. Because we can no longer provide updated components, it will no longer install with new Office setups. This applies to: Access 2019 volume licensed and Enterprise plans Access 2021, Access 2024, and Microsoft 365 subscriptions Access 2021 and Access 2024 as part of the Office 2021 and Office 2024 perpetual licenses (standalone versions) DatabaseCompare.exe is installed typically under the DCF folder of your Office installation (for example, C:\Program Files\Microsoft Office\Office16\DCF\DATABASECOMPARE.EXE), and it often comes alongside Microsoft Spreadsheet Compare as part of Office Professional Plus or Microsoft 365. In addition, supporting DLLs and configuration files are located within the same DCF subfolder. These files handle database connections, reporting, and comparison functions. These files will be removed. If you're running an older version of Office and have a working version of this tool, you can continue to use it until June 20, 2026. After that, it will be removed and will not be available for download. Therefore, we advise you to find a replacement for Database Compare. You can find similar standalone tools that compare two Access databases from other vendors: AccessDiff: This tool easily compares all objects in Access, including forms, code modules, queries, macros, and more. It is designed to help users retrieve lost software and compare all objects in Access databases. AccdbMerge: This tool is an easy-to-use diff and merge tool for Microsoft Access database files. It compares table definitions, data, forms, modules, and more. A free version is available for the main database objects. DataWeigher: This tool compares and synchronizes data between two MS Access databases. It provides a visual result with each type of record (added, deleted, changed) represented by a different color. The comparison results can be saved as a report or SQL script for data synchronization. Total Access Detective: This tool allows you to find differences between any two objects in one Microsoft Access database, including fields, controls, properties, macro lines, module code, and data. It also supports comparing two blocks of text from text files on disk or the text you copy and paste. We recognize this change may require planning, and we encourage customers to review these alternatives and plan a transition away from Database Compare ahead of its retirement in June 2026.Multi-line Text Box misleading text and cursor display
Starting with 365 Version 2603 on 4K monitor, in a multi-line text box, typing multiple words followed by line feeds (Enter key) then moving cursor back up to previous line causes trailing characters to disappear, entering characters at the end of the line shows the new character with the cursor in front of it, and other bizarre behavior. Selecting all the text shows it is all there but trailing characters at the end of a line can disappear depending on cursor position. If I change the monitor resolution to 2K, the issue goes away. If I rollback to version 2602 the issue goes away. This is an issue with version 2603 on 4K monitors. We have many customers reporting the same issue.
Office 365 no internet error
Outlook just stopped working yesterday. I have been using 356 for a couple of years now. One drive and Outlook both say I don't have internet access. Obviously I do. I can use one drive and outlook via a web browser, but not the desktop apps. I have tried most of the suggested fixes and nothing has worked. Anyone else having issues?Access fixes released in Version 2603 (Build 19822.20114)
Here's a summary of bug fixes in the latest version of Access: Bug Name Issue Fixed 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. Please continue to let us know if this is helpful and share any feedback you have.
