Thanks for the response, Art.
That's a good point about changes in the system tables. However, in my case, the "Numeric value out of range" error occurs when trying to perform an `Update()` on a C++ `CRecordset` object that operates on a user-defined table, not on system or catalog tables. The flow is: I open the recordset, edit a field, and the error is thrown when calling `Update()`. This makes me suspect that the difference in how the ODBC driver (now 4.10) handles writing data back might be key. I would like to test with the 4.50 driver, but unfortunately, my current development environment is 32-bit, and I don't have a compiled version of my program to test on a 64-bit system. Could there be any specific configuration in the 4.10 driver that I should review, or any known differences in its behavior when performing `Update()` operations compared to previous driver versions?