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. If you want 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 non-multithreaded applications on Linux/Unix, use libdblib12.so and libdbtasks12.so.

For non-multithreaded applications on Mac OS X, use libdblib12.dylib and libdbtasks12.dylib.

If the client application uses encryption then the appropriate encryption support (dbecc12.dll, dbfips12.dll, or dbrsa12.dll) should also be included.

If the client application uses an ODBC data source to hold the connection parameters, your end user must have a working ODBC installation. Instructions for deploying ODBC are included in the Microsoft ODBC SDK.

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