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 libdbodm16.

For Windows, the sacshelp16.chm help file can be installed to provide local context sensitive help when using the Microsoft ODBC Data Source Administrator. If the help file is not locatable, then an attempt will be made to go to DocCommentXchange using the system's default Internet browser.

For Windows Vista or later versions of Windows, you must include the SQL Anywhere elevated operations agent (dbelevate16.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 [LL]. There are several message files each supporting a different language. To install support for different languages, you have to include the resource files for these languages. Replace [LL] with the language code (for example, en, de, jp, and so on).

For Windows, the ODBC Configuration for SQL Anywhere and Connect to SQL Anywhere window support code (dbcon16.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.