>>1) The difficulty of application version-transitioning?
>>2) Economic implications - Maybe this tactic will discourage MS clients from upgrading?
>
>They do now, Bruce < s >. They don't seem to have "beta'ed" this very well.

Good, it sounds like I may have missed a lot of useful complaining :-)

Perhaps they will change the EULA to allow for reasonable upgrade time periods, it sounds like. I was just beginning to picture my home & office, each with a row of PCs with labels on them: "vfp6. vfp7. vfp8. vfp9..."

I mean, really, the more I contemplate it, the stupider (valid word?) that EULA seems! I still like to keep vfp5 & 6 loaded on at least one machine, so I can go back and check whether bugs or features (and whatnot) existed previously, or are only in a newer version, maybe. Most of do a little of that, probably, and sometimes it's even moderately important to make such checks. Certainly when offering advice to others, we may need to do this sort of version checking.

>>...where many of us must do simultaneous support for 2 app versions, for at least a brief window of time during a roll-out period.
>
>Right, and many for much longer, what with obsinate clients and all.

Indeed.