You will need to install all the requirements (DLLs and OCXs) to each workstations. Then you will be able to launch the EXE that is on the server. Otherwise, you will get error 429 (ActiveX can`t create component).

If you really don`t want to install anything on the workstations, you may have a look at Terminal Services. The application will run somewhere on a server and it will be accessed through the browser.


>I created a program that a user wants to install on the server and then run the exe from workstations. The problem is that when the program is installed several required dlls and ocxs are installed that are required to run the program. So if the user wants to use it they have to run the install on the workstation and then the complete program is installed locally.
>
>If the app is run from the server is it possible to write code that
>
>1) When the app is run at a workstation it checks to see if each of the required files exist (I think there are 5)
>
>2) If the file(s) don't exist then have the files copy from the server to the workstation and register the ocx, dll and mark as shared (I know I can register using resrv32 is it possible to mark as shared through code?)
>
>Does this sound reasonable? Some of the files are copied to winnt\system32 Is it possible to get at these files through code even if there isn't permissions?
>
>The other thing that is required is mdac but I'm thinking that I could either a) have the mdac.exe launch if the correct version is not installed (how do I check that?) or b) send a message that mdac needs to be updated to the user and kill the app
>
>Thoughts on this? Anybody have a better solution? I realize I could create another install with just the required files but I don't want to make the user have to download two files 10+MB big if I can do it programatically. I figure this will cut down on support questions or frustatration with the product when custemers are getting errors like ActiveX object could not be created.
>
>Thanks!