The Visual FoxPro 9.0 upgrade version will install for the same earlier versions as VFP 8 did, that is, as far back as VFP 5 or Visual Studio 97 (Professional or Enterprise). See
I saw this article at which said that the EULA for VFP 7 and other, earlier software includes this sentence: "A Software Product labeled as an upgrade replaces and/or supplements the product that formed the basis for your eligibility for the upgrade."
Starting with VFP 8 and other MS products, the EULA specifically stated "Upgrades. To use a version of the Software identified as an upgrade, you must first be licensed for the software identified by Microsoft as eligible for the upgrade. After upgrading, you may no longer use the software that formed the basis for your upgrade eligibility."
The article concluded, "Should you upgrade to VFP 8, buy a full version of VFP 8, or buy MSDN? If you're using more than one Microsoft developer product, the answer is simple: MSDN is cheaper. If you develop only in VFP, it's a harder call."
A later article said this about VFP 9 at "One important product-related question arose. When VFP 8 came out, many developers were disappointed to discover that buying an upgrade version meant you had to uninstall VFP 7 (or whatever version you used for the upgrade) before installing VFP 8. (See my column in the June 2003 issue.) Ken Levy said this will not be required for VFP 9. Even if you buy an upgrade, you'll be able to run the new and old versions side by side."
In my case, I don't care about trying to run older VFP versions and so don't need multiple installations, but posted the above as the results of my internet searches.
And a nice aspect of switching from 8 to 9 is that 9 is 100-percent compatible with anything written in 8. Like turnng out a switch in one room and turning on a switch in another room.
dbMark
I saw this article at which said that the EULA for VFP 7 and other, earlier software includes this sentence: "A Software Product labeled as an upgrade replaces and/or supplements the product that formed the basis for your eligibility for the upgrade."
Starting with VFP 8 and other MS products, the EULA specifically stated "Upgrades. To use a version of the Software identified as an upgrade, you must first be licensed for the software identified by Microsoft as eligible for the upgrade. After upgrading, you may no longer use the software that formed the basis for your upgrade eligibility."
The article concluded, "Should you upgrade to VFP 8, buy a full version of VFP 8, or buy MSDN? If you're using more than one Microsoft developer product, the answer is simple: MSDN is cheaper. If you develop only in VFP, it's a harder call."
A later article said this about VFP 9 at "One important product-related question arose. When VFP 8 came out, many developers were disappointed to discover that buying an upgrade version meant you had to uninstall VFP 7 (or whatever version you used for the upgrade) before installing VFP 8. (See my column in the June 2003 issue.) Ken Levy said this will not be required for VFP 9. Even if you buy an upgrade, you'll be able to run the new and old versions side by side."
In my case, I don't care about trying to run older VFP versions and so don't need multiple installations, but posted the above as the results of my internet searches.
And a nice aspect of switching from 8 to 9 is that 9 is 100-percent compatible with anything written in 8. Like turnng out a switch in one room and turning on a switch in another room.
dbMark