Non-Unicode Application with the OpenAccess SDK ODBC Driver

An operation involving a non-Unicode application and the OpenAccess SDK Unicode driver incurs some overhead because function conversion is involved.

Windows

The process is as follows:

1. The non-Unicode application sends ANSI function calls to the Driver Manager.
2. The Driver Manager converts the ANSI function calls to UCS‑2/UTF-16. It passes the Unicode function calls with UCS-2/UTF-16 argument values to the OpenAccess Client for ODBC.
3. The OpenAccess driver returns UCS-2/UTF-16 argument values to the Driver Manager.
4. The Driver Manager converts the UCS-2/UTF-16 argument values to ANSI and returns these argument values to the application.

Linux/UNIX

The Driver Manager converts the ANSI function calls to UTF-8. It passes the Unicode function calls with UTF-8 argument values to the OpenAccess Client for ODBC. Conversion is based on the code page-specific value in IANAAppCodePage, which must be set to the code page of the system’s locale.