>>But will it technically be enforced? That's something I sorely need to know, as a license-manager for vfp at my agency. Other vfp8 users may not be as scrupulous, and I can't watch everyone all the time, what with credit card purchasing being virtually untrackable - particularly if users use the product on machines I can't "watch" through our network.

First, let me restate that "unscrupulous" remark I made. That's a very small issue, as fed hirees are screened so thoroughly we won't have many unscrupulous users. It's the "ignorance factor" that really will be the problem - many users accustomed to the old EULAs will not likely re-read the new one, let alone read *any* EULA at all.

To some other posts: I know others have said every user SHOULD READ every new EULA, but that's a joke to expect. I don't disagree, I'm just stating the impracticality, it simply ain't gonna happen. It's going to be up to people like me to enforce as well as I can, which is limited.

>Yes, it sure is making it hard for you to do a proper job.
>And on further thinking, *if* it was going to be automatically enforced then it would have to do the removing of VFP7 itself, else how would it know that you qualified for the upgrade in the first place? LATER: well it could ask for the CD, but that can't be it if it is installed (VFP7).
>My guess is that it is a trust style of "enforcement".

Yes, that could be difficult, now that you mention it. It's a sort of "reverse" enforcement technique, and could be a practical difficulty, that could be defeated by anyone knowledgeable enough, if not done extremely tightly. And then the potential technical problems with partial installs that abort, etc...