Unicode in an ODBC application
View the typical ODBC application architecture.

In this scenario, if an application calls to Unicode enabled APIs, then it must be connected to a Unicode enabled Informix® ODBC Driver (Version 3.8 and later) to ensure that there is no loss of data. If the application calls to ANSI ODBC APIs, the application can be linked to either a Unicode enabled driver or an ANSI driver.
The Informix® ODBC Driver continues to support Informix® GLS. Hence all data fetched in character buffers are fetched in the client locale code set. Only data fetched with wide character buffers use Unicode.
On Windows™, if the ODBC driver is not Unicode enabled, the ODBC Driver Manager maps all Unicode API function calls to ANSI ODBC APIs.
For details about how the Windows™ ODBC driver manager handles mapping, see the section "Function Mapping in the Driver Manager" in the ODBC Programmer's Reference for Microsoft™.