Access fixes released in Version 2408 and 2409

Bug Name 

Issue Fixed  

Access terminates unexpectedly when you copy a row that contains some Unicode characters 

Copying all Unicode characters should now work correctly 

Access 365 Runtime displays the incorrect product name in the Installed Products list 

After installing the Access 365 Runtime, the Installed Products list displayed “Microsoft Access Runtime 2016”, but will now display “Microsoft Access Runtime 365” 

Bug Name 

Issue Fixed  

Errors when using importing or linking to txt, csv and Excel files located on the network 

In some cases, an attempt to import or link to a text or Excel file could result in the error “Error 3051 - The Microsoft Access database engine cannot open or write to the file. It is already opened exclusively by another user, or you need permission to view and write its data.” 

This could happen if another application had opened the file, even if it did not require exclusive access. Access will no longer require exclusive access to a file to read from it for this purpose. 

ODBC Data Sources application does not provide option to create new dBase connections when Office 365 is installed 

The Access Database Engine supports connections to dBase files, but this capability was not exposed to the ODBC Data Sources application. 

Bug Name 

Issue Fixed  

Error 3048 and Hanging Access Task 

There were multiple underlying issues that contributed to this behavior, and fixes were delivered to multiple versions, but this should now be resolved in all active builds. 

Error when trying to link to/import Salesforce tables 

This issue impacted multiple versions, and is resolved in Current Channel, Monthly Enterprise Channel, and Semi-Annual Channel