>
No, you were suggesting that VFP developers should adopt and learn .Net is quickly as possible to save themselves.
<

To save themselves???? I don't think I said that. I did say that VFP developers should learn .NET in order to expand their skill sets as a hedge against what is becoming a tighter and tighter market. If you want to label it as saving themselves, that is up to you...

<<
My point is that VFP is not a special case here.
<<

The knife cuts both ways on this. If on one hand, VFP is not a special case, then VFP developers should get in lock step with everybody else and expand their skill sets. If on the other hand, VFP is a special case, VFP developers should be expanding their skill sets. Whether they do it with .NET or not is another issue. The important thing is to expand your skill set to the point that you are not dependant on Fox-only work.

<<
Your doctrine would apply as much, if not more so to the VB developers who "have precious little experience with frameworks and use a language that was object based, not object oriented.", to quote my previous post.
<<

In some ways, the VB developers are better prepared for .NET than VFP developers. In other ways, Fox developers are better prepared. I would not be too quick to judge and to be too dimissive (sp.) of the VB camp. And


>>Maybe in your neck of the woods there is...
>
>I can only comment on my own experience in this regard despite the fact that I am currently consulting on a VFP job in the Philippines. Hardly my neck of the woods, so, go figure <s>.
>

One job and your own experience does not a healthy market make. It begs the question of why you had to go to another continent to find Fox work???