#Odbc driver for sql server windows#

If you are using a relational database, why would you be allowing such frequent changes? And given such changes, why would you expect any framework to work well with such a thing? Honestly, the expectation that you can 'get away with that' is not realistic. However, you haven't indicated anything other than you have a custom error message and that you have a schema that changes regularly. Frameworks are not going to handle that kind of thing well. Net, I'd not be happy to work correctly if the schema for my data was changed behind my back, and nobody told me about it. Well, I don't know about you, but if I were a framework, such as.

#Odbc driver for sql server windows#

Application Server OS Windows Server 2012R2 64-bit SQL Server 2017 (.1), OS - MS Windows Server 2016 Standard 64-bit I have already attempted using different API conversions for dates. Once that time has passed 'restricted data type attribute violation' error comes back.

While the time has not fully passed, the recordset will attach, open, and operate on this table like nothing is wrong. This error will repeat twice in a row and then will not replicate again for a while. The issue is that this recordset class will fail to open the table with the error 'Restricted data type attribute violation'.

The application attempts to bind with the table using a CRecordset class (dynamically bound). This issue occurs repeatedly with a table with columns that are somewhat managed dynamically in the sense that columns may be added or removed on occasion.