>>We are upgrading to ISX (Full version) and this is one of the reasons. ISX LE does not allow installation if the software already exists on the system. The user must uninstall it and tehn run the Setup.EXE again to install the lates version.
>>
>>I believe it reads the information in the Installed Software registry keys to know whether the application has beed installed previously.
>
>The limitations of ISX LE version that comes with VFP7 is why I am looking to upgrade to ISX. I downloaded the ISX eval version. I looked at the UpgradePaths option in the project tree, but I am a little confused as to how/if updating [overwriting] installed files with newer ones if I provide a new SETUP.EXE to the users.
I just looked at it (eval version as well). I wasn't able to add a new Upgrade Path by selecting the previous EXE. You may have to open the old ISM and copy the Upgrade Code from the General Information screen into the Upgrade Path property sheet.
Good luck.
BTW, I was able to create a test install with the eval version, create a new install and point the Upgrade Path to that EXE. It did retrieve all the information for the upgrade path.
Larry Miller
MCSD
LWMiller3@verizon.netAccumulate learning by study, understand what you learn by questioning. -- Mingjiao