Database Exchange > Working with the Web Client - Introduction > Preparing Database Exchange for Web Deployment

Preparing Database Exchange for Web Deployment

By default, DatabaseExchange.ocx and its dependent files are not packed and ready for web deployment. In the current version (V6.00 r1), users have to prepare the cab file themselves. Refer to the projects Example or CSV_Example where the file ActiveX.zip packs this control. But this file includes DatabaseExchange.ocx file only and not its dependent files.

The following table lists all components required by DatabaseExchange.ocx. Some of these dependent files are part of operating system; others are constituent controls and libraries, and installed by applications such as CitectSCADA and Microsoft Office. If the components highlighted in the table don't exist on the target machine, the Database Exchange control won't work since Web Client deployment doesn't install them either. In the current version, no cab file includes these files in the Web deployment. If you are missing these files, follow the instructions below as a workaround.

Component Name

Operating System

Registry

Location

ASYCFILT.DLL

x

C:\WINDOWS\system32

comcat.dll

x

x

C:\WINDOWS\system32

msvbvm60.dll

x

x

C:\WINDOWS\system32

oleaut32.dll

x

x

C:\WINDOWS\system32

olepro32.dll

x

x

C:\WINDOWS\system32

stdole2.tlb

x

C:\WINDOWS\system32

Comdlg32.ocx

x

C:\WINDOWS\system32

msado25.tlb

C:\Program Files\Common Files\System\ado

MSADODC.OCX

x

C:\WINDOWS\system32

MSBIND.DLL

x

C:\WINDOWS\system32

msdatgrd.ocx

x

C:\WINDOWS\system32

msstdfmt.dll

x

C:\WINDOWS\system32

VB6STKIT.DLL

C:\WINDOWS\system33

To manually install the components required by DatabaseExchange.ocx:

  1. Copy and paste the files highlighted above from your server machine to their corresponding locations as shown in the Location column. Be aware that Windows 2000 and Windows NT 4 use WINNT as the windows directory.
  2. Create a batch file, say RegComponents.BAT, and paste the following contents into the file and save it.
  3. Run the batch file to register these files.
  4. Redeploy the Web Client and run it.