Feedback
Did this article resolve your question/issue?

   

Article

The SQL Server driver fails to update data in a datetime field when using a cursor.

Information

 
TitleThe SQL Server driver fails to update data in a datetime field when using a cursor.
URL NameThe-SQL-Server-driver-fails-to-update-data-in-a-datetime-field-when-using-a-cursor
Article Number000116507
EnvironmentProduct: Connect for ODBC SQL Server Wire Protocol drivver
Version: 7.1.06.0438, 08.02.0365
OS: All support platforms
Database: SQL Server
Application: All supported applications
Question/Problem Description
The Connect for ODBC SQL Server driver fails to update data in a datetime field when using a cursor.
This problem occurred in both 7.1 and 8.0 version of the driver.
Steps to Reproduce
Clarifying Information
An update to a SQL Server datetime field fails.
No error message is displayed.
The app is doing a parameterized current of cusor update or setpos.
Error Message
Defect NumberDefect XDBC-15867, XDBC-26510
Enhancement Number
Cause
The driver was not handling the update of a datetime field corrently when cursors are used.

 
Resolution
Fixed in hot fix 07.16.0439.
Fixed in hot fix 08.02.0381.

Refer to  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 6:50 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.