I feel the need to add my three cents:

To say the available pool is shrinking is an understatement. I can attest thru my own experience that we received very few resumes from qualified VFP people when looking. All the people who were on the top of my list ended up taking dotnet positions. I've also watched several ads on places like dice. They started out asking for VFP people. Several months later the same ad appeared asking for dotnet people willing to learn VFP.

I posted an ad several months ago where the recruiter mentioned how hard it was to find a VFP person, so their requirement was someone skilled in MS technologies. And of course I got slammed here as if it was my fault.

>If the decision is yours, then you're doing so with the knowledge that someone other than you may ultimately need to maintain that app. And the # of qualified and available VFP people is shrinking.


It must be 2 to 3 yrs ago that Jim Duffy posted here that 100% of the people attending his VFP training sessions were working on maintaining an existing VFP app. No new dev.

>Bottom line....and I mean this literally....and I'll take on all the flaming....anyone doing "File....New Project" in VFP for client work is quite likely doing a disservice to his/her client. I don't mean that in a mean or snide way, it's just the truth.

>

Bragging will not accomplish a darn thing. I've worked with several people in the past who were VB/VB.net programmers who ending up working with me on VFP projects for whatever reason. When the project ended, they moved back to VB/VB.net, no questions asked. They saw nothing that they would miss. Continuing to think that VFP is the end of the world in development tools is kidding yourself.
>Thirdly, brag about it to every developer and geek you speak with. There are so many good things about VFP that, with a little practise you'll be able to diplomatically crush any argument they come up with.