Feedback
Did this article resolve your question/issue?

   

Article

Conversion failed errors occur inserting timestamps into SQL Server

Information

 
TitleConversion failed errors occur inserting timestamps into SQL Server
URL NameConversion-failed-errors-occur-inserting-timestamps-into-SQL-Server
Article Number000158971
EnvironmentProduct: Connect for ODBC SQL Server Legacy Driver
Version: 7.1
OS: All supported platforms
Database: SQL Server
Application: All supported applications
Question/Problem Description
Conversion failed errors occur inserting timestamps into SQL Server with the Connect for ODBC SQL Server Legacy Driver
Steps to Reproduce
Clarifying Information
Error Message[DataDirect][ODBC SQL Server Legacy Driver][SQL Server]Conversion failed when converting date and/or time from character string.
Defect Number
Enhancement Number
Cause
The exact cause of the issue was not identified. The Connect for ODBC SQL Server Legacy Driver may not support all the functionality of the newer SQL Server databases. When connecting to versions of SQL Server that are later than SQL Server 2000, it is recommended to use the Connect for ODBC SQL Server Wire Protocol driver.
Resolution
Switching to the Connect for ODBC SQL Server Wire Protocol driver resolved the issue.

Both SQL Server drivers are currently shipping with Connect for ODBC version 7.1 (December 2016).



 
Workaround
Notes
Last Modified Date12/20/2016 3:11 PM
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.