Victor,
Are you saying that you think the "required VFP9" clause is to remove any tendency to "hold out" on version upgrades now that a newer version/release is announced?
My take: we know we have support until 2014. We have the next VFP "something" announced that is not something completely off the wall (e.g. some more VFP emulation classes for dotNET) since it requires VFP9. For those of us who have VFP9: cool, a newer release is announced. For those of us who don't: no chance of leapfrogging versions as you've done since VFP6 ;-) so you might as well upgrade now and use the VFP9 benefits.
Regards
j.R
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
