>
>I'm convince that if Visual FoxPro 8 would be called VFP .NET we wouldn't be having this conversation....
>

Then switch to a .NET language. If VFP8 was VFP.NET, it would not be VFP anymore, all of its current data handling advantages would be gone, and you would have a whole new learning curve to deal with.

I'm really not trying to get on your bad side...I'm just trying to give you more to consider. I agree with Michel's comments on this. The tool does the job, and does it well. I think one of the biggest concerns with VFP might be the difficulty in finding a large pool of programmers that know the tool well.