The following table shows the files needed for a working SQL Anywhere ODBC driver. These files should be placed in a single directory. The SQL Anywhere installation places them all in the operating-system subdirectory of your SQL Anywhere installation directory (for example, bin32 or bin64).
The multithreaded version of the ODBC driver for Linux, Unix, and Mac OS X platforms is indicated by "MT".
|Linux, Solaris, HP-UX||
|Linux, Solaris, HP-UX MT||
|Mac OS X||
|Mac OS X MT||
For Linux and Solaris platforms, you should create a link to the .so.1 files. The link name should match the file name with the ".1" version suffix removed.
There are multithreaded (MT) versions of the ODBC driver for Linux, Unix, and Mac OS X platforms. The file names contain the "_r" suffix. Deploy these files if your application requires them.
For Windows, a driver manager is included with the operating system. For Linux, Unix, and Mac OS X, SQL Anywhere provides a driver manager. The file name begins with libdbodm11.
Note that for Windows Vista or later versions of Windows, you must include the SQL Anywhere elevated operations agent (dbelevate11.exe) which supports the privilege elevation required to register or unregister the ODBC driver. This file is only required as part of the ODBC driver install or uninstall procedure.
A language resource library file should also be included. The table above shows files with the designation [xx]. There are several message files each supporting a different language. If you want to install support for different languages, you have to add the resource files for these languages.
For Windows, the Connect window support code (dbcon11.dll) is needed if your end users will create their own data sources, if they need to enter user IDs and passwords when connecting to the database, or if they need to display the Connect window for any other purpose.
|Discuss this page in DocCommentXchange.
Send feedback about this page using email.
|Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|