Feedback

Feedback

Did this article resolve your question/issue?

   

Article

Why do I see W functions in an ODBC trace when the application is ANSI

Printable View

Information

 
TitleWhy do I see W functions in an ODBC trace when the application is ANSI
URL NameWhy-do-I-see-W-functions-in-an-ODBC-trace-when-the-application-is-ANSI
Article Number000128304
EnvironmentProduct: Connect for ODBC
Version: All supported versions
OS: All supported platforms
Database: All supported databases
Application: All supported applications
Question/Problem Description
Why do I see W functions in an ODBC trace when the application is ANSI
My application is ANSI but UNICODE calls are present in an ODBC trace.
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
The application was compiled to use UNICODE.
Resolution
Application call functions are set at compile time. For example SQLConnect will become SQLConnectW when an application is compiled on Windows.

On UNIX/Linux there are UNICODE compile flags which can be set in the compile statement which will cause the same behavior.
Workaround
Notes
Last Modified Date2/10/2016 4:07 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.


Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.

Progress, Telerik, Ipswitch, Chef, Kemp, Flowmon and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.

Terms of Use Privacy Center Security Center Trademarks License Agreements Code of Conduct Careers Offices
Do Not Sell My Personal Information