Access releases bug fixes in version 2506

Bug Name

Issue Fixed

Error when trying to run append query

When an update/append query qualified column references (e.g., Table1.Field1) the reference might fail to resolve and produce an error reading “The INSERT INTO statement contains the following unknown field name: Table1.Field1”

Error when trying to save or run a query containing certain characters

For queries containing some Unicode characters, attempting to run or save the query could generate the error “The SQL statement is invalid.”

Can't create a query directly in SQL view

We have now added a button to the Queries section of the Create ribbon to allow you to create a new query opened to the SQL editor, rather than the QBE (Query-By-Example) designer

Exporting data to a text file might export some characters incorrectly

When exporting data containing some Unicode characters and choosing the “Export data with formatting and layout” option, invalid characters would sometimes be output to the text file.

Using the clipboard to transfer data from tables/queries to text did not work for some Unicode characters

Access was not rendering text from tables/queries with the CF_UNICODETEXT format so when you copied a table/query from the Navigation Pane, then pasted into a destination that accepted text, Unicode characters might not be preserved

When exporting to Email using the HTML format Unicode characters might not be preserved

Some characters would be replaced by question marks rather than preserving the original content when exporting to HTML Email

When exporting a table with a relationship but no lookup defined Access may hang during the validation step

During export Access tries to create a lookup in Dataverse that corresponds to a lookup defined in Access for related tables. However, if a relationship was defined but there was no lookup defined for the foreign key, then Access could hang during the export process.

If the Display Form option is set in the Options dialog, then any time the Options dialog is closed you incorrectly get a message saying that you must close and reopen the database for changes to take effect

This could happen even if no changes were made. Access will now only generate this message if you really do need to close and reopen the database for changes to take effect.