Learning VFP aint that tough.

Depends on how much one learns.

It's not knowledge of a programming language that makes for a good developer. Lots of watch makers can build a timex. Very few can build a rolex.

You could assemble a team like this much more quickly and in the long run maximuze productivity.
This assumes a team is required to deliver the project. Sometimes one person, with good technical support, is better able to deliver than a group. For big projects Like VFP or VB (RAD tools) - that have the budget and time to build a solid team (eg Fox Team), a team is important - for little projects - like end user apps - perhaps a team is not required.

Its good to have a mix of people including some who are 'not married to VFP'.
Perhaps a history of solid deliveries and good references would promote the project goals more than an ability to recite the help manuals of a given language. What ever tool that will deleiver the project on schedule and on budget should be the first priority.