>>Excellent, Michel, but when I said "why wait for VFP 9.0?", I meant let's talk about renaming VFP right away. This is the perfect opportunity to act without delay, so that the official release of VFP 8.0 is the release of VFP.NET. If that requires the release date to be pushed back by a month, I think most people would agree it's well worth it, compared to suffering through an extra year of VFP marketing limbo. It can't hurt to ask...
>
>Ok, while we do it, how would formulate that question assuming it would contain Yes, No, I have no opinion, in the list of choices?

It has been proposed that the name of Visual FoxPro 8.0 be officially changed to Visual FoxPro.NET, aka VFP.NET, upon its forthcoming release in early 2003. This would not entail any functional changes to the product, but purely a change in the way that VFP is presented and marketed. Instead of being an adversary of .NET, VFP would become a part of it, thereby changing both people's perception of VFP and the VFP community's perception about .NET. Do you agree, and would you be willing to endorse an immediate letter to Microsoft to that effect?

1. Yes
2. No
3. (no opinion)