>>>
>>>In my case, I've always had the executable run from the network. It runs app files also on the net. Much of the functionality that the apps utilize is accessed via dynamic linking back in the original executable. I've never had a performance problem with this sort of setup. However, this may not be the case under circumstances different from mine.
>>>
>>Thanks George,
>>
>>Historically, I too run my apps from the server. And this one would be no different except that it's the first app which uses an activeX control. So what you're saying is that the ActiveX control needs to reside on the local machine while the app / data are on the server? This is the approach I thought makes the most sense as well, but now I'm faced with the problem of getting the ActiveX control onto each machine.
>>
>>Can I create a "setup" disk that has only the control? If so, please tell me how, I've tried to do this several times with no success. I don't really want to have to install the entire application just to get the ActiveX control installed locally. What I'd like to see is a setup routine that installs/registers the ActiveX control, then copies a desktop shortcut which points to the app on the server.
>>
>>Any suggestions?
>>
>Hi Larry,
>
>Sure, but I think the best thing to do would be to explain how I handle it.
>
>I've created a generic installation exe (called Install.exe) which is installed on the user's machine, then run as a post-setup executable. It uses information in a table to do the real work of creating shortcuts, writing the config, etc. (and delete its own). I use my LNKFILES.DLL for this. When I create the disk images directory, I add whatever ActiveX controls, and in Step 6, make sure that they're indicated as being in the WinSysDir. This takes care of registering the controls.
>
>Being a corporate developer, I have advantages that I wouldn't have otherwise. The users are told that they may not change the installation directory. It's also documented that the run-time library and the INSTALL.EXE that's put on their hard drive may be deleted after the installation is complete.
>
>This help?

Believe me George... everything helps! :)

Thanks!