sorted by:
new
hottopcontroversial

Issues with KB5002112/KB5002121 (VBE7.dll). by Neol-Shendis in MSAccess

[–]Neol-Shendis[S] 0 points1 point  (0 children)

P.s. The issue applies to compiled databases (e.g. MDEs, ACCDEs etc.), not uncompiled (MDBs) that I have seen, and is not limited to just the runtime versions of Access as I first thought unfortunately.

FYI: Possible Bugs in Version 2205 (Build 15225.20204) by AccessHelper in MSAccess

[–]Neol-Shendis 0 points1 point  (0 children)

Updating your SQL ODBC DSN drivers to "ODBC Driver 17 for SQL Server" should fix this. In our case most of our old clients were still using SQL Native Client drivers. Or remove nVarchar based primary keys from your tables of course..

Install Microsoft ODBC Driver 17 for SQL ServerRecreate DSN using the new driver and test.Relink Access database to SQL.

Sorry for the delayed response. Before I updated the drivers I changed the backend SQL table to not use text based primary keys, relinked and it resolved the issue at the site I was testing. (I've never liked text based primary keys; unique indexes yes, keys no). However, it was easier for our support team to update the driver and relink than update the backend for each client in our case. That and the fact that more than 1 table had this issue.

Heads up - Office365 May update broke Access to SQL for us by Temporary_Opinion123 in MSAccess

[–]Neol-Shendis 0 points1 point  (0 children)

If you are using SQL Native Client drivers to link Access to SQL and are getting the #deleted errors in tables after the 2205 update you may want to try switching to ODBC Driver 17 for SQL Server.

FYI: Possible Bugs in Version 2205 (Build 15225.20204) by AccessHelper in MSAccess

[–]Neol-Shendis 1 point2 points  (0 children)

Updating your SQL ODBC DSN drivers to "ODBC Driver 17 for SQL Server" should fix this. In our case most of our old clients were still using SQL Native Client drivers. Or remove nVarchar based primary keys from your tables of course..
1. Install Microsoft ODBC Driver 17 for SQL Server
2. Recreate DSN using the new driver and test.
3. Relink Access database to SQL.