ODBC CLI

ODBC (Open Database Connectivity) is a standard call level interface (CLI) developed by Microsoft Corporation. It is based on the SQL Access Group CLI specification. ODBC applications can run against any data source that provides an ODBC driver. ODBC is a good choice for a programming interface if you want your application to be portable to other data sources that have ODBC drivers.

• ODBC conformance
  SAP Sybase IQ provides support for ODBC 3.5, which is supplied as part of the Microsoft Data Access Kit 2.7.
• ODBC application development
  Every C/C++ source file that calls ODBC functions must include a platform-specific ODBC header file. Each platform-specific header file includes the main ODBC header file odbc.h, which defines all the functions, data types, and constant definitions required to write an ODBC program.
• ODBC Samples
  Several ODBC samples are included with SAP Sybase IQ. You can find the samples in the %ALLUSERSPROFILE%\SybaseIQ\samples\SQLAnywhere\C directory (Windows) and $SYBASE/IQ-16_0/samples/sqlanywhere/c directory (UNIX).
• ODBC handles
  ODBC applications use a small set of handles to define basic features such as database connections and SQL statements. A handle is a 32-bit value.
• ODBC Connection Functions
  ODBC supplies a set of connection functions. Which one you use depends on how you expect your application to be deployed and used:
• Server options changed by ODBC
  The SAP Sybase IQ ODBC driver sets some temporary server options when connecting to an SAP Sybase IQ database. The following options are set as indicated.
• SQLSetConnectAttr extended connection attributes
  The SAP Sybase IQ ODBC driver supports some extended connection attributes.
• 64-bit ODBC considerations
  When you use an ODBC function like SQLBindCol, SQLBindParameter, or SQLGetData, some of the parameters are typed as SQLLEN or SQLULEN in the function prototype. Depending on the date of the Microsoft ODBC API Reference documentation that you are looking at, you might see the same parameters described as SQLINTEGER or SQLUINTEGER.
• Data alignment requirements
  When you use SQLBindCol, SQLBindParameter, or SQLGetData, a C data type is specified for the column or parameter. On certain platforms, the storage (memory) provided for each column must be properly aligned to fetch or store a value of the specified type. The ODBC driver checks for proper data alignment. When an object is not properly aligned, the ODBC driver will issue an "Invalid string or buffer length" message (SQLSTATE HY090 or S1090).
• Result sets in ODBC applications
  ODBC applications use cursors to manipulate and update result sets. SAP Sybase IQ provides extensive support for different kinds of cursors and cursor operations.
• Stored procedure considerations
  This section describes how to create and call stored procedures and process the results from an ODBC application.
• ODBC escape syntax
  You can use ODBC escape syntax from any ODBC application. This escape syntax allows you to call a set of common functions regardless of the database management system you are using. The general form for the escape syntax is
• Error handling in ODBC
  Errors in ODBC are reported using the return value from each of the ODBC function calls and either the SQLError function or the SQLGetDiagRec function. The SQLError function was used in ODBC versions up to, but not including, version 3. As of version 3 the SQLError function has been deprecated and replaced by the SQLGetDiagRec function.