ODBC datetime format 'III' causing timestamp to time conversion to fail? - response (1) by dnoeth

Hi Jennifer,
when you check DBQL for the bad query you'll probably see that the ODBC driver replaced TIME with INT, this setting is not only for DDL :-)
'III' should not be used anymore (it's just a stupid old default), better use 'AAA' or 'IAA'.
 
Or set another ODBC option "Disable Parsing", which also switches off other ODBC functions like RTRIM, LENGTH, MONTH, etc.
 
Dieter