>>In my environment creating install disks for every modification simply isn't practical. The applications reside on the servers, and because of multiple users the actual install simply copies the necessary runtime files and controls to the local machine and creates the icons and folders by means of a post-setup executable.
>
>You don't have to actually make physical disks for that, of course. I was just thinking that a program like InstallShield, which is designed to handle this sort of thing, might be better than reinventing the wheel.

True, but at the time, I didn't have it.

>>One the things that happens during the initialization of the main exe (applications are usually app files) is that it checks to make sure the controls are up to date.
>
>For example, what happens if the controls are not up to date, but they're being used by another app (or the OS), so that you can't just copy over the old versions? InstallShield can take care of this by updating the controls after rebooting.

To date, this hasn't been a problem. That's not to say it may not be in the future. Maybe it's because we use mostly PowerBuilder and Lotus. The PowerBuilder folks don't use ActiveX controls.

>Don't get me wrong: I'm sure you've thought about all of this and have a solution that works perfectly well. :)

So far, so good. Having to maintain and support 40+ applications by myself sometimes causes me to resort to taking "short cuts" like this. I will say this, that if ActiveX controls do become a problem in this regard, I will look closely at InstallShield.