question

GianluigiSellitto-2979 avatar image
0 Votes"
GianluigiSellitto-2979 asked GianluigiSellitto-2979 edited

ADO 2.8 and Compatibility mode

If you have old code, that access Sql Server through MS-ADO 2.8, you can have some trouble if connect to DB on Sql Server 2016 with compatibility mode do 2016 (130). You can experience some random error on update:

Row cannot be located for updating. Some values may have been changed since it was last read.

The error is absolutely random. On the same table one row update go, the next no.

The only solution is to set compatibility level to 2014 (120) or 2012 (110).

sql-server-general
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Another solution to the problem: use Provider=MSOLEDBSQL.1 instead of Provider=SQLNCLI11.1 in connection string. With Sql Native Client provider there is a problem with row update, with the new Microsoft OLE DB Driver for SQL Server there is no problem.

Bye.

0 Votes 0 ·

1 Answer

AmeliaGu-msft avatar image
0 Votes"
AmeliaGu-msft answered

Hi GianluigiSellitto-2979,

Thanks for sharing the workaround.
In addition, MDAC/WDAC components might be removed in future releases, and no new features will be added to components in MDAC/WDAC and it isn't recommended to use them for new application development. And when you upgrade or modify existing applications, remove any dependency on these components. Please refer to this article which might help.

Best Regards,
Amelia


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.