Hmm see what you mean.

The name should end in .NET for sure



>IMO, The next version of VFP should be named consistently with visual studio.
>
>It's not about being cute, but about _MARKETING_ and the message that product "packaging" sends to the public. If we get VFP 7.0 side by side with VB.NET and VC.NET IN VS.NET, most IT managers will assume that VFP is not really part of the suite at all.
>
>And some of you will jump stating that IT managers are usually not qualified to make programming decisions, but guess what, MOST IT decisions are made by these individuals.
>
>Alex
>
>PS: I'm surprised that MS is adding the .net moniker after seeing the results of Novell doing the same a while back (netware 3 -> INTRAnetware 4 -> netware 5).
>
>>Ricardo mentioned this week that the Foxteam has not decided what the name of VFP7 will be. With tongue firmly planted in cheek, let's try to help them out:
>>
>>VFP.NET - pretty likely
>>VFP.COM - we make money off it, no?
>>VFP.NEXT
>>Evan
>>VFP+
>>VFP++
>>VB9 < s >
>>Seven - then the next version would be Seven Up
>>VFP2001
>>Joe
>>F#