ODBC error when adding or modifyiing an entity - but for one customer only!


We get this error:

at one customer where we have basically no control over the environment.

Same exact code, in dev, in test and in our production environment works flawlessly.

Have you seen anything like this before?


You should check which SQL/ODBC driver is installed at your customer. You should try to update it to the latest version.
Are you using latest TMS XData version?

I am using mORMmot for remoting and we really should solve this on our side, because the customer has an extremely large and complex infrastructure, so they are very rigid around what is and is not available/allowed.
We have no direct access to their infrastructure, only mediated by their internal tools.

I don't see what is the relation with Mormot? Is it relevant?
If your customer computer doesn't have the needed prerequisites (like an old SQL Server client), you should ask them to update their environment.
Are you using latest TMS Aurelius version?

Hi, yes, but it turned out not to be a problem with the driver or aurelius but a missing conversion from the mORMot string type to Delphi.

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.