|
The simplest way to deploy OLE DB client libraries is to use the Deployment wizard. For more information, see Using 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, win32 or x64). For Windows, there are two provider DLLs. The second DLL (dboledba10) is an assist DLL used to provide schema support. There is no second DLL for Windows CE.
| Description | Windows | Windows CE |
|---|---|---|
| OLE DB driver file | dboledb10.dll | dboledb10.dll |
| OLE DB driver file | dboledba10.dll | N/A |
| Language-resource library | dblg[en]10.dll | dblg[en]10.dll |
| Connect dialog | dbcon10.dll | N/A |
OLE DB providers require many registry entries. You can make these by self-registering the DLLs using the regsvr32 utility on Windows or the regsvrce utility on Windows CE.
For Windows clients, it is recommended that you use Microsoft MDAC 2.7 or later.
When deploying OLE DB applications to Windows CE devices, you must also include Microsoft's ADOCE version 3.1 (or later). At minimum, the following files are required.
adoce31.dll adocedb31.dll adoceoledb31.dll msdadc.dll msdaer.dll msdaerXX.dll (where XX is the 2 letter country code, EN for English)
The Microsoft Data Access Components (MDAC) files msdadc.dll and msdaer.dll must be registered on the device.
For more information, see Creating a Windows CE database.