>Unless that would be to VFP.Net (with everything that says). I don't see it helping foxpro

That's an interesting point. I mean, about the VFP.Net name.

I agree that changing the name won't make a difference to its current status/recognition, as this seems the focus on this and similar threads. However, a VFP.Net name for an upcoming version would be nice. Especially that Visual FoxPro integrates more and more with .Net.