Feedback
Did this article resolve your question/issue?

   

Article

SQLDescribeCol returns incorrect data type when CASE clause is used

Information

 
TitleSQLDescribeCol returns incorrect data type when CASE clause is used
URL NameSQLDescribeCol-returns-incorrect-data-type-when-CASE-clause-is-used
Article Number000175477
EnvironmentProduct: Connect64 for ODBC SQL Server Legacy driver
Version: 07.14.0055 (b0067, U0135)
OS: Linux X64
Database: SQL Server 2012 SP3
Application: all supported applications
Question/Problem Description
When a SQL Statement contains a CASE clause, SQL Server CHAR data type is described as SQL_DATE / SQL_TYPE_DATE (ANSI / UNICODE)
Steps to Reproduce
Clarifying Information
Note 1 : When the SQL Statement does not contain a CASE clause, the SQL Server CHAR data type is described as SQL_CHAR
Note 2 : This is only reproducible when running against SQL Server 2012 SP3 (SQL_DBMS_VER = 11.00.6020)
Note 3 : This does not reproduce on Windows 
Error Message
Defect NumberDefect 52849
Enhancement Number
Cause
Resolution
Fixed in hot fix 07.16.0075 (b0103, U0212).
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
Use the Connect64 for ODBC SQL Server Wire Protocol Driver
Notes
Last Modified Date11/7/2016 8:43 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.