Hi,

We have an ActiveX component which clients can install either by downloading a CAB file or by running an MSI installer. The component consists of an OCX file and some support DLLs. Regularly, updates are made to the component.

When a client has an old version of the component which was installed via the MSI installer, and then tries to download a newer version via CAB files, the following problem occurs:

- The existing OCX and DLL files in the program files directory (where they were registered by the MSI installer) are replaced by the newer versions from the CAB file

- New DLLs that did not exist in the previous version are extracted into "c:\windows\downloaded program files", causing the component not to find them once loaded.

Any idea on why this happens or how to work around this? Ideally, all files from the cabinet would get extracted and registered in the Downloaded Program Files folder. I was looking for information on the rules used by the CAB file installer but couldn't really find what I was looking for.

Thanks,

Wouter