Feedback
Did this article resolve your question/issue?

   

Article

Error "STRING REPRESENTATION OF DATETIME VALUE HAS INVALID SYNTAX" with ODBC DB2 driver

Information

 
TitleError "STRING REPRESENTATION OF DATETIME VALUE HAS INVALID SYNTAX" with ODBC DB2 driver
URL Nameerror-string-representation-of-datetime-value-has-invalid-syntax-with-odbc-db2-driver
Article Number000178559
EnvironmentProduct: Connect(64) for ODBC DB2 Wire Protocol driver
Version: 07.16.0247
OS: Linux
Database: DB2
Application: Test application
Question/Problem Description
The error below occurs when binding DATE and TIME with SQL_C_CHAR and SQL_CHAR.
Steps to Reproduce
Clarifying Information
Error Message[DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for iSeries and AS/400]STRING REPRESENTATION OF DATETIME VALUE HAS INVALID SYNTAX.
Defect NumberDefects 48487, 55190
Enhancement Number
Cause
The driver was incorrectly formatting the data.
Resolution
Fixed in hot fix 07.16.0253.
Refer to article  Connect and Connect64 for ODBC hot fix download and install instructions for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date11/20/2020 7:19 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.