>>Please excuse me for being rude by chiming in here. If you are truly looking out for your employer, you must consider how difficult it is to find a knowledgeable VFP programmer should you leave. I am having the most difficult time finding someone locally who knows more about FoxPro than how to spell it.
>>
>
>Jack,
>As Evan have already said, you bring up a good point. I'm in a similar situation now. I've be totally rewriting a FPD2.6 app to Windows and I'm not sure I should convert to VFP or VB! The problem is I'll be leaving this company to work full-time in another company after this project and I'm concerned I won't be able to find qualified VFP programmer to replace me here after I'm gone.
>
>I'm considering using VB since you can find more programmers that use VB but I don't want to use Jet (what an ironic name) and SQL Server is available but who'll maintain this beast after I'm gone (it's a small shop)??
>
>It seems like I have a hard decision to make real soon.
>
>John.


IMHO, Although it may be easier to find a programmer with VB experience, I'm not so sure it is easier to find one with proper experience in database programming in VB. I agree that it might be a little more difficult to find an experienced VFP programmer, but almost anyone who is experienced in VFP has a fairly adequate skillset. I think this is due to the fact that if you use VFP for development, you have to get pretty good at it to use it. In contrast, everyone and their brother can pick up a VB book at the bookstore and claimi VB experience. (I hope no one will misunderstand what I'm saying. I'm not knowcking VB at all, I just think that the RATIO of qualified VFP programmers to total VFP programmers is probably higher than that of qualified VB programmers to total VB programmers.)

Just my couple of cents worth,