Forum Discussion
Version 16.0.15225.20204 - Problems with Runtime
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
Perhaps, then, you are being impacted by a different problem. Sorry, but in the flurry of reports about this bug, it is easy to assume such problems are all caused by it.
If your tables worked properly up until the day of the update, it's hard to think of any other reason, though.
Can you delete and relink the tables? When you do that, do it in a back up copy of the accdb.
Make sure that all tables have a valid Primary Key and that you designate it as the Primary Key if Access asks you to do that. If any of those Primary Keys are of NVarchar datatype, this bug did impact such tables. Again, if your tables use such NVarchar datatype fields as Primary Keys, and relinking doesn't correct the problem when linked using ODBC Driver 17 or 18, then there could be some other, yet to be determined problem.
- Actually we are working with postgresql databases and the postgresql ODBC driver ...
This problem appears with the last update of Microsoft Access (full version not runtime)
Indeed using a serial type in postgres is the same as adding a sequence but in our databases several codification tables are using varchar column type as primary key, this solution works but will bring lot of work and tests for ou Microsoft Access applications
According to your remark i am going to try with the ansi driver to see it it makes a difference- Yes, sorry. You are working with Postgres, not SQL Server. Too many bugs, too little time.
