It's not as easy as "just replace the ActiveX control". If the replacement ActiveX control doesn't have the same progID, you'll have to rebuild your application so it recognizes the new control. Odds are, the replacement control, even if from the same vendor, will have a different progID, making rebuilding and redeploying the application a necessity.

>Hi All,
>
>What's the best practice in swapping out an older set of ActiveX controls (dbi-tech's ctexplorer etc.) for a newer one? The app is client-server, where the controls are installed on the local workstations, usually, but not always, in the \Windows\System32 folder. Forcing thousands of users to uninstall and then re-install the app is not an option. Oddly, dbi doesn't have an answer.
>Thanks.
>
>Luke