>That's a great idea! But why wait for VFP 9.0? And let's also add a proviso that whenever it happens, it be VFP.x, where .x is whatever MS is calling the premier developer toolset it promotes, supports, and sells. Also understand that the appelation VFP.NET means nothing as far as VFP itself is concerned. We need not assume that VFP.NET in any way implies a redesign around the CLR. This is purely an act of marketing, and an expression of sincere commitment to a reasonably large number of long-time Microsoft customers. MS has assured the VFP community it is not planning to crush VFP or force us to switch to .NET unless and until we're persuaded that this is the best course to take, right? What would it cost to change the name from VFP to VFP.NET? I strongly believe that the benefits to Microsoft of such a change would be well worth the cost.

I agree. With all that and other related points, I think UT could release a survey on knowing the perception of the community as to know if they'd prefer a VFP 9.0 naming versus VFP.NET.