MX 2.x)

Migrating Applications from NonStop ODBC Server

HP NonStop SQL/MX Connectivity Service Manual—524944-008

A-11

ODBC API calls

ODBC 2.x compliant applications do not need to be migrated to support the new 3.x

functions. The Microsoft ODBC driver manager allows version 2.x applications to run

using version 3.x-compliant drivers and vice versa. It automatically maps version 2.x

application functions to version 3.x-compliant drivers, version 3.x application functions

to version 2.-compliant drivers, and it performs mapping between 2.x and 3.x functions

and parameter options.

ODBC/MX includes a 3.5-compliant ANSI driver; it does not include a Unicode API.

However, the driver manager automatically provides the mapping between the Unicode

API and the ANSI API.

Table A-1 shows how ODBC 2.x calls map to ODBC 3.x, and whether NonStop ODBC

and ODBC/MX support each call.

Table A-1. ODBC API Mapping Between 2.x and 3.x Versions (page1of3)

ODBC 2.x Calls* ODBC 3.x Calls*

3.x Calls

Supported by

ODBC/MX?

2.x Calls

Supported by

ODBC Server?

SQLAllocConnect SQLAllocHandle YY

SQLAllocEnv SQLAllocHandle YY

SQLAllocStmt SQLAllocHandle YY

SQLBindCol SQLBindCol Y Y

SQLBindParameter SQLBindParameter Y Y

SQLBrowseConnect SQLBrowseConnect Y Y

No equivalent SQLBulkOperations N N

SQLCancel SQLCancel Y Y

SQLColAttributes SQLColAttribute YY

No equivalent SQLCloseCursor Y N

SQLColumnPrivileges SQLColumnPrivileges Y N

SQLColumns SQLColumns Y Y

SQLConnect SQLConnect Y Y

No equivalent SQLCopyDesc Y N

SQLDataSources SQLDataSources Y Y

SQLDescribeCol SQLDescribeCol Y Y

SQLDescribeParam SQLDescribeParam Y N

SQLDisconnect SQLDisconnect Y Y

SQLDriverConnect SQLDriverConnect Y Y

No equivalent SQLDrivers Y N

SQLError SQLGetDiagField YY