>>Again - what's in it for Microsoft to do this? Microsoft didn't give in to VB6 crowd (as they well shouldn't have) and they surely won't give in to the much, much smaller VFP community.
>
>But VB was not canceled. Not the same thing here.

Tell that to the die hard VB6 folks who refuse to move to VB.NET. Functionally it's actually very similar to the VFP case as there is no real upgrade path from VB6 to VB.NET...

>> But it's a hurdle that one gets over and then and only then does the benefit kick in.
>
>True and hope it's fast to learn!

Well, depending on what you choose in most cases it isn't <s>...

>But many forget the small and mom and pop companies that don't have the thousands to invest in rewriting something that work for them.

There's little need to re-write. I think the focus is on going forward with new developelopment. If you have an app that work or that needs moderate enhancements then there's little need to rewrite IMHO.

>Like I mentioned in another thread, if they make a SP3 to support the next OS then I will make my peace(but won't like it in secret ;) )

FWIW we were told that an SP3 is not out of the question although unlikely.
But I would also venture to say that the current push of technology (Vista/.NET 3.0 platform environment) will be here for a while to stay, so the next major OS changes are probably a long while off...