Forum Discussion

uehninger's avatar
uehninger
Copper Contributor
May 29, 2022

Version 16.0.15225.20204 - Problems with Runtime

I have update today to the may release 16.0.15225.20204 - now i have Problems to start our Access Runtime Application. I get a message 3167 Record has delete - but their is no Record deleted. After ...
2016
access
Hywel_Evans's avatar
Hywel_Evans
Copper Contributor
Just re-linking the table worked for me.
Changing the primary key might not be needed.
JoneSh77's avatar
JoneSh77
Copper Contributor
May 30, 2022

Hywel_Evans 

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

  • George_Hepworth's avatar
    George_Hepworth
    Silver Contributor
    May 30, 2022

    JoneSh77 

     

    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.

     

     

    • JoneSh77's avatar
      JoneSh77
      Copper Contributor
      May 30, 2022
      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


      • George_Hepworth's avatar
        George_Hepworth
        Silver Contributor
        May 30, 2022
        Yes, sorry. You are working with Postgres, not SQL Server. Too many bugs, too little time.
    • cbgbnyc1's avatar
      cbgbnyc1
      Copper Contributor
      Jun 06, 2022

      not true odbc SQL Server 17 driver  still giving me #deleted

      • JoneSh77's avatar
        JoneSh77
        Copper Contributor
        Jun 07, 2022

        Hi,
        I have Microsoft Access Version 2205 Build 16.0.15225.20172 64bits version
        Since friday it works again for me with sql server and with postgresql
        Best regards

Resources