The MaxDB ODBC driver supports UNICODE. This means that the functions listed below are also available, irrespective of whether the data source supports UNICODE or not.
On Microsoft Windows, the Driver Manager uses the UNICODE variants of the ODBC API. If, for example, the SQLConnect function is called within the application, SQLConnectW is called in the ODBC driver. The conversions between ASCII and UNICODE are performed by the Driver Manager.
Overview of the functions that are defined in the MaxDB ODBC driver for access to UNICODE data
SQLBrowseConnectW
SQLColAttributesW
SQLColAttributeW
SQLColumnPrivilegesW
SQLColumnsW
SQLConnectW
SQLDataSourcesW
SQLDescribeColW
SQLDriverConnectW
SQLDriversW
SQLErrorW
SQLExecDirectW
SQLForeignKeysW
SQLGetConnectAttrW
SQLGetConnectOptionW
SQLGetCursorNameW
SQLGetDescFieldW
SQLGetDescRecW
SQLGetDiagFieldW
SQLGetDiagRecW
SQLGetInfoW
SQLGetStmtAttrW
SQLGetTypeInfoW
SQLNativeSqlW
SQLPrepareW
SQLPrimaryKeysW
SQLProcedureColumnsW
SQLProceduresW
SQLSetConnectAttrW
SQLSetConnectOptionW
SQLSetCursorNameW
SQLSetDescFieldW
SQLSetStmtAttrW
SQLSpecialColumnsW
SQLStatisticsW
SQLTablePrivilegesW
SQLTablesW