Forum Discussion
Version 16.0.15225.20204 - Problems with Runtime
- I found the Problem - this Release has a Problem to use an SQL-Server table with a Primary Key of three fields (integer, nvarchar, nvarchar). In all older Versions this works in the new version it work not. The Tableview in Access shows all rows but each row shows the entry record deleted.
Workaround:
I changed the Fields to varchar an use another PrimaryKey. Now it works.
Changing the primary key might not be needed.
Hi,
I think i have a similar problem but relinking the table is not enough.
I can not access my tables if the primary key is a varchar.
For the moment my only issue is to add a serial , make it the primary key and add a unique constraint corresponding to my former primary key ...
The problem seems to be linked to the last update (Version 2205 build 16.0.15225.20172-64bits)
Is the problem identified by Office team ?
Thank you for your response
Yes, this newest bug release is widely discussed in several forums.
I didn't know that it impacted the runtime as well, but version 2205 has this and other problems.
The solutions include changing the Primary Key fields from NVARCHAR to VARCHAR, or preferably, to an Identity integer or even to a sequence (which is what you did I suspect?)Also, it has been confirmed that ODBC drivers for SQL Server 17 and 18 are not impacted by this problem.
not true odbc SQL Server 17 driver still giving me #deleted
