We understand and support the update process for replacing shared files such as DLLs in the Windows folder, but for files in our INSTALLDIR, we always want to replace them. We run into problems when users modify some of those data files which end up with Modified Dates later than what we're trying to install. If we have Always Overwrite checked for those files in our build, our update works fine. The problem is that we sometimes forget to set that when we update our InstallShield file configurations (e.g. we choose the same file names from another folder). They default to NOT overwrite. Is there a way to always overwrite all files in a folder and/or a programmatic way to verify all the files in a folder are set to Overwrite so we don't make a setup build that omits that? Thanks. ... View more

When the setup program runs and detects an upgrade situation, the user is prompted that an upgrade will occur. That's nice but we want to verify the user is entitled to the upgrade (in case they already returned it for a refund). We have routines that authenticate the user (same as when they install for the first time), but do not know where to put that code for an update. I also can't seem to debug it. It just shows the prompt and starts updating it. Is there an Event that's triggered when it goes into update mode? It's also odd that sometimes the prompt appears to update, while other times, it just goes to the Modify/Repair/Remove screen. Is there an event to capture their selection after that? We want to validate them for modify and repair, but want everyone to be able to Remove it. ... View more

I need the setup program to have Administrator privileges to install some DLLs, however, it should only be installed for one user, not the whole machine. If I don't require administrator, everything installs in the right user location, user registry, and shortcut menus appear for the user. If I require administrator execution level for the setup, when the user runs it, it prompts for the administrator login as expected. However, it installs everything for the "Administrator" rather than the user, so everything is private and fine for the Administrator but isn't available for the original user. That is, if the Administrator logs in, it shows up on the Start menu, the files are visible, etc. When the user logs in, nothing is available. What am I doing wrong or does a setup which requires Administrator login automatically become available to everyone who logs into that PC such that it's really installed on the Local Machine?  Thanks in advance for your help and insight.   ... View more

We have a product "MyProduct Basic" that people install. We create updates for the product and just change the version number in InstallShield, When the setup program is run, if it detects it's installed, it upgrades it. If not, it performs the full installation. Works great! We created a new Product Configuration with a new name (e.g MyProduct Pro). We want that setup to be similar to the upgrade and the Basic version if it's already installed. Because the product name changed, that doesn't happen even though I have it using the same product GUID (or not). Neither works.. Is there a way to update the existing installation and change the name so it replaces the existing program on disk and in the Windows Control Panel Add/Remove Programs list? Without that, we are forced to tell the user: 1. Uninstall the existing version and install the new one, or 2. Have our setup program keep the old program name (so Basic stays forever) which would confuse people if they go to the control panel list since the thought they own the Pro version. For new installations, it would say Basic when it should be Pro, so that's unacceptable. Not sure what I'm missing to handle this. Thanks in advance. . ... View more