I've never looked for VFP programmers. I always look for VB or Access programmers. They show up and are used to having to work REALLY HARD to get the results that they want. In order to train them efficiently, it would help to have a Rosetta stone on staff, a guy who speaks VB and VFP. So, he can train them from the position that they are seeing it. "See this property sheet? Works just like VB except, if you right click it, it doesn't close... etc."

Wait until you see the look on a VB guys face when you show him a remote view of a SQL table. (Make sure you have some smelling salts.)

The three Access/VB'er's that I hired and trained for my last company all went on to greater jobs in Milwaukee writing FoxPro code when our company threw us out. Yep, the boss did what you are considering and announced that we were all going to be learning VB/Access. We four jumped ship and got raises. Hang in there. Don't use available programmers as your deciding factor for picking a language. Look at how much more quickly your VFP team can develop an app than the best VB team.

... but, then again, I could be wrong.

Marty