Renaming could still make sence if they rename also all Visual Studio products, say to VisualComponents2000++ :) Then nobody will be able to tell where is VB and where is VFP... :)

>The best time that MS should have changed the name is when VFP came out. VFP was so different from FPW that just adding Visual to the name was not enough. Now it's too late and a name change will only propagate the idea that Fox is diying IMHO.
>
>As for Visual X, I'm against. VFP has it's root in xBase and that's the only relation it has with it. But adding ++ would be a good idea IMHO, since it would stand out that it is OOP.

---

>At the risk of starting a lengthy, useless thread -- does anybody else feel, as I do, that "FoxPro" is a dumb name? Saying it out loud makes me squirm!
>>
>>I am aware of the proud history of the FoxPro name, but nonetheless I hate it. How about "Visual X" (as in "xBase") for the next release? It sounds cool and streamlined, and would make it look right at home alongside other Microsoft development tools. (But please, no "++"!)