>OK. Everyone is entitled to their opinion < s >
>
>Now I seem to recollect that VFP8 has been changed to assist in mitigating the impact of the MSKB #293638 and that the recommended fix is to open the table using VFP7 and PACK it. This of course may have changed in the final version, but this is what I remember from the VFP public beta Help for a new error message near the end of that part of the Help.

I couldn't say for sure if it's been fixed, but there were several builds after the public beta. Odds are, it was taken care of.

>
>IF (and it's a BIG "IF") that's still in there, then I guess that people who want to adopt that fix will have to either buy the FULL version so that they can keep VFP7 installed OR deinstall VFP8, reinstall VFP7, PACK, deinstall VFP7 and reinstall VFP8.
>
>As regards your statement "...if you go back and read older licenses, they imply the same thing, but it isn't clear cut as it is now.", nothing could be further from the truth as I see it!
>From section #7 of my EULA for VFP7 "...A SOFTWARE PRODUCT labeled as an upgrade replaces and/or supplements the product that formed the basis for your eligibility for the upgrade. You may use the resulting upgraded product only in accordance with the terms of this EULA." it is quite clear that "supplements" is in addition to the word "replaces" and "supplements" can in no way be construed as unclear, can it?!?!?
>

I guess it depends on your interpretation of the word "supplements".