The simplest way to deploy OLE DB client libraries is to use the Deployment Wizard.
If you want to create your own installation, this section describes the files to deploy to the end users.
Each OLE DB client computer must have the following:
A working OLE DB installation OLE DB files and instructions for their redistribution are available from Microsoft Corporation. They are not described in detail here.
The SQL Anywhere OLE DB provider The following table shows the files needed for a working SQL Anywhere OLE DB provider. 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). For Windows, there are two provider DLLs. The second DLL (dboledba12) is an assist DLL used to provide schema support.
|OLE DB driver file||dboledb12.dll|
|OLE DB driver file||dboledba12.dll|
|Elevated operations agent||dbelevate12.exe (Windows Vista or later only)|
The table above shows a file 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).
OLE DB providers require many registry entries. You can make these by self-registering the dboledb12.dll and dboledba12.dll DLLs using the regsvr32 utility.
Note that for Windows Vista or later versions of Windows, you must include the SQL Anywhere elevated operations agent which supports the privilege elevation required when DLLs are registered or unregistered. This file is only required as part of the OLE DB provider install or uninstall procedure.
For Windows clients, it is recommended that you use Microsoft MDAC 2.7 or later.
Discuss this page in DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|