I don't think anybody is having a problem understanding this. I think the original post was a statement about why there may not be a new version of VFP which is a very worthy topic of discussion, imo. The statement that "there aren't enough new ideas for VFP" or even "there aren't enough upgrades of vfp" to justify another version are extremely debatable subjects although it may not matter since MS has it's own agenda anyway. I would just like better .NET VFP interop examples from MS. I think a lot of developers don't want to be forced to rewrite VFP apps in C# or VB.NET, but, probably wouldn't have a problem using them in conjunction with one another and, possibly, do a gradual migration. You'd think that MS would like this too since it would mean the purchase of VFP9 in addition to the latest VS.NET...

>Why is it so hard for some folks to understand that MS is providing a nice BIG window for VFP developers to learn other technologies? In particular, .Net.