Feedback
Did this article resolve your question/issue?

   

Article

Different Date Data Types between SQL Server Legacy and Classic driver

Information

 
TitleDifferent Date Data Types between SQL Server Legacy and Classic driver
URL NameSQLDescribeCol-different-between-SQL-Server-Legacy-driver-and-SQL-Server-Classic-driver
Article Number000175580
EnvironmentProduct: Connect for ODBC SQL Server Legacy driver
Version: 07.14.0055 (b0067, U0135)
OS: all supported platforms
Database: SQL Server
Application: all supported applications
Question/Problem Description
SQLDescribeCol returns different values for date between SQL Server Legacy driver and SQL Server Classic driver :
With the Connect for ODBC SQL Server Legacy driver, SQLDescribeCol returns Date data type as SQL_WVARCHAR.
With the Connect for ODBC SQL Server WP driver, SQLDescribeCol returns Date data type as SQL_DATE or SQL_TYPE_DATE (ANSI or UNICODE)
Steps to ReproduceDDL to reproduce problem:

CREATE TABLE [dbo].[TAB_00362423](
[SETL_DT] [date] NOT NULL
) ON [PRIMARY]

Steps to reproduce problem:
- SQLPrepare("select SETL_DT from TAB_00362423")
- SQLDescribecol()
Clarifying Information
Error Message
Defect NumberDefect 52861
Enhancement Number
Cause
Resolution
Fixed in hot fix 07.16.0076 (b0103, U0212) for Unix and hot fix 07.16.0063 (b0102, U0211) for Windows. 
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/16/2016 8:17 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.