Typically this file will point to a third-party ODBC Driver Manager library. Linux and Unix systems do not come with a default ODBC driver manager - a separate driver manager must be downloaded and configured. This tells the application at load time to attempt to load the libodbc.so library file from the system path specified by the LD_LIBRARY_PATH environment variable. libdbodbc16.so)ġ. Linking against the generic ODBC driver manager available on the Operating SystemĪn example of a gcc application compile that would reference a generic ODBC library uses the switch '-lodbc': Link against a specific ODBC driver and provide all connection information inside the ODBC program (e.g.Link against a specific ODBC driver manager library (e.g.Link against the generic ODBC driver manager library available on the system (e.g.The choice of how to link against the ODBC libraries at runtime is then up to the ODBC application developer: unixodbc.h is included in the SQL Anywhere SDK directory. In order to reference the ODBC API library, an ODBC program will refer to 'unixodbc.h' in its #include section and is then linked against a named library when it is compiled. ODBC is an application programming interface (API) that is invoked by the client program to connect to a database server. For a list of available ODBC API commands that a program can use, see Microsoft's ODBC API reference. Understanding Linking for ODBC Applications on Linux and Unix Operating Systems

Note: The SQL Anywhere command-line tools can use ODBC data sources (DSNs) for information about connections, although they may not necessarily use ODBC as the actual connection mechanism to the database server - many will use the DBTools or the DBLIB / Embedded SQL libraries internally.

Sql anywhere odbc driver