>
That is because a few hundred VFP developer are as productive as a few thousand .NEt developers....
>

That is a myth - that VFP developers are presumptively more productive than anybody else - whether they are VB or .NET developers. It is the same argument that many trot out that because VFP has had full OOP capabilities - Fox developers are better at OOP than their counterparts - such as those in the VB world.

The logical fallacy here is Post Hoc Ergo Propter Hoc - which means that after this therefore because of this. To say that one thing - just because it follows from something else - that there is some sort of cause effect relationship is not necessarily true and in reality - is rarely true.

The truly productive VFP developers are productive because they are good developers - not because they are VFP developers. An good developer can be orders of magnitude more productive than an average developer - regardless of the tool. Productivity and the innate skill of a developer transcends a toolset.

That said - does it mean that a good VFP developer will necessarily be a good .NET developer? No - since perhaps the good VFP developer's knowledge is entirely predicated on teh "VFP Way" of doing things. That said - just because one may be a good VFP developer - it does not mean he or she is a good developer in general. Good developers in general can and will be productive in any tool. They find a way - that is what makes them good - that is what makes them productive. Remember - its the fiddler - not the fiddle.