Installer for VFP project that includes updates and upgrades

Transfer data from a typical Inno setup to an Inno setup designed for multiple products, including updates and upgrades. The setup must be ‘turnkey’, ready to use. The setup needs to do the following: Download Updates and Upgrades: A process needs to be created for the website that permits the user to download the update or the upgrade installer to the local computer. Initial Install: Each of the five products already has an Inno setup script (.iss). Although they are essentially the same, they need to be reviewed and modified to ensure that only files that are needed are installed. The installers for the five main products need to work and look similar to the installers that will be developed for updates and upgrades. The following functionality is not in the installers for the five main products, but needs to be added: 1.) If the user tries to install over another version or another product, the installer needs to notify the user that an application is already installed. The name of the product and the version number needs to be displayed for both the installed application and the application that is about to be installed. 2.) When a different product or version is already installed, the installer needs to warn that data could be lost when the database is uninstalled. The user then needs to have the option to a.) continue the installation and replace the entire application, including the database, b.) continue the installation but give the user the option to automatically backup the database before continuing, c.) continue the installation but leave the database as-is without affecting its data, d.) quit the installation so the user can manually uninstall or, just exit without making any changes. If the user selects option ‘b’ the installer needs to back up the database to a location chosen by the user. An initial installation requires a product key to go beyond the trial period so TurboActivate must appear after installation. Once the product key is entered and continues to be correct, TurboActivate should not appear on start up. TurboActivate can still be accessed from one of the Tools menus. A product key is emailed after the purchase. Some of this functionality is already part of the initial installers. Updates: This can include updating an older installed version of Standard to a newer version of Standard, an older installed version of Pro to a newer version of Pro, and so on. Each of the five products needs an Inno setup script (.iss). The scripts need to create installers that remove a old file and insert a newer file or that copy new files over older. [login to view URL] is the main file. The product name and version number of the installed application needs to be compared with what is in the installer. Do not permit the upgrade if they are different products, for example, if the user tries to install a BizDoc Enterprise upgrade on the BizDoc Standard application. The product name and version number of the installed application and the name and version of the update need to be displayed. An update does not require a new product key so TurboActivate should not need to appear right after the installation. It can be opened from one of the Tools menus in the application for deactivation, etc. Upgrade: Uninstalling one product and installing a more costly product is an upgrade. For example, the owner has BizDoc Standard and purchases an upgrade to BizDoc Enterprise. Upgrades do not require reinstalling the database. Upgrades do require a new product key so TurboActivate needs to appear on application startup after installing the upgrade. If the product key is entered and continues to be correct, TurboActivate should not appear on application start up.