Hi, Mark.

IMO, if MS didn't change FoxPro name when they launched VFP, that could be fairly considered a very different product from older versions, it is ingenuous to think about a name change. I can't see clearly what will be the advantage for MS, neither for us, but even so, a product name change is not something a company could do if not for VERY compelling reason.



>Yes I see your point that we should conentrate on the .net deabte first.
>
>However if we do decide to stay out, then maybe we can get a name change out of MS somehow.
>
>But its pointless worrying about it until the .net thing is sorted out.
>
>Fair comment:)
>
>>>I agree that a name change is a priority.
>>>
>>>Trouble is finding one we all agree with.
>>>Hows about
>>>
>>>MS Solution
>>
>>Seriously, I don't think a name change is even remotely possible HUGE product change. And if MS will decide to make such a radical change, most surely it would have to do with integrating it with .Net anyway, what leaves us again in the debate about whether or not is desirable for VFP to be integrated (see previous Wikis on this topic).