Automatically Download/Register ActiveX Components

[Silver30]

I am curious to know how others have approached this situation...

A standard VB executable resides on a public network drive (no application or web server) and shortcuts to this executable are placed on hundreds of client desktops. The executable is later upgraded to include activeX components not previously included. When a user launches the program from a client, the program needs to recognize the client's lack of support for the added activeX components, download them from the server to the client, register them, and continue to run the program. The idea is not having to manually touch the clients after the initial installation.

Has anyone dealt with this before?

Thanks.

 

[Foada]

Here is a link that might help

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q173091

It shows how to register the ocx programmatically. You will have to trap the error when the app can't create the ocx and then download it and register it. Hope this at least gets you started. If you choose to battle wits with the witless be prepared to lose.