> How many of the developers who migrated from VFP to .NET
> did so because of the overwhelming technical advantage?

I have to admit, I actually CHOOSE to use C# instead of VFP to import a certain COBOL file into Oracle 9i where the number of fields and the extreme size of the field names (bordering on verbose data descriptions) precluded an "easy" VFP solution. But that doesn't change my opinion of C#. I still think it's a brain-dead version of C++ aimed to make general programming easy, to generate new training and certification revenue, to tie graduates and corporations alike to a particular platform, and to increase the number of available programmers competing for positions for companies who don't like paying for experienced professionals.

> How many did so because the market for VFP development
> has dried up so drastically and this was the logical carear
> progression?

I am still investigating an alternative to VFP for when that day finally arrives, but I have not found a suitable replacement yet, and I suspect the platform on which it runs will not be Windows.