Hi John,

I don't disagree that you will likely be able to leverage .NET into the future more so than VFP. I simply point out that in order to keep the cash register ringing MSFT tends to create an impetus for a technology Para dyne shift at a faster rate than the stated life cycle of many of their products. Given that there will likely be something beyond .NET within the next "x" years and given that the tool we use now (VFP) is supported for at least then next 6+ years, the $64 million question; "Is this the time to make a change?" If nothing else; is .NET technology mature enough today?

What if MSFT realizes that despite their own marketing hype .NET does not address all the things that VFP does and that to abandon VFP would be to expose an Achilles heel in the non-enterprise database market, that may be quickly filled by a competitor.

All interesting thoughts to ponder.....