The old Native Client drivers are affected by this bug as is the even older default SQL Server bug from 2000.
For whatever reason, the newer ODBC drivers such as version 17 aren't affected.
In theory these are also more efficient and have better performance BUT the driver will need to be installed on each user's workstation.
My 2 cents as well.
We have about 150 users using our ACCESS application with linked tables to there SQL server.
We always used the Native driver 11.0 to establish the DAO (linking the tables) and ADO connection (direct queries to the SQL server). Since this issue arrived we were, sort of, obligated to use the newer driver(s). By doing this we also separated the DAO and ADO connection strings, where the DAO (ADODB) connection string uses the ODBC 17 SQL Driver and the ADO connection string uses the latest OLE Driver 19.
I also tested it with ODBC driver 18 but this does not seem to work (also getting the record is deleted error)...
By using the new drivers the error does not appear in the latest office build 2205, BUT one thing that is drawing my attention is that the DAO queries (requesting / opening forms with more records) is
A LOT slower than the native 11 client... This seems to be even more so when the end user uses a SQL 2012 server.
Any of you know what is causing this? The strange thing is that at some of our users, which are using SQL server 2019, and overall have a better performing server, the new drivers are not particularly slower than the native 11 driver. Though I can't imagine that the different drivers can have this much speed-impact on the different servers.