When VFP came out, I had never worked in any version of FoxPro or FoxBase or whatever. In fact, my experience in programming with Windows consisted of about 4 months of VB programming. But I did learn how to program in DOS with different languages. Windows was just another platform (better, it turns out). VFP was just another language (better, it turns out).

Why look for a VFP programmer? Look for a good programmer who is an intelligent person and can learn VFP. I think a lot of things are a lot more important when hiring someone than requiring that they know the development language. It all depends on your situation.

There are some advantages to hiring an employee who has no programming experience in the language being used. He/she will be learning the language while applying your standards and styles. He/she will not have any bad habits in the language. This is a big one. You have the knowledge to get a new programmer onto the right track. I did not have this guidance. I have learned some bad habits on my own. I am breaking them, but some people have bad habits that aren't being broken. You can teach them the proper way of doing things from day one.

Joe


>I am a technical manager who's been searching for VFP programmer's now for about 6 month's in the detroit area. I myself have been programming VFP since it's birth. We just cannot find any VFP programmer's. We have to consider a new approach.. maybe VB, and Access or PowerBuilder. I want to hear from some people in the same situation who can tell me of their success or failure with VFP. I feel as if we're heading down the road to no where with VFP, and pretty soon they'll be no turning back.
>
>Jeff