It is nothing more than the law of supply and demand. The pool of VFP developers - expert level - is very small. If you have an app that needs work - you are going to pay. The pool of VB developers is very large. I would say that it is far easier to find an expert level VB developer than it is to find an expert level VFP developer.

I don't think it has a damn thing to do with the developer per se.

My point relates to the person faced with 2 job prospects. If the better rate is with VB - and you are qualified - if you stay in VFP for the sake of staying in VFP - that makes no sense to me...

< JVP >


>Hmmmmm....
>
>What I have seen is that VB work is in a wide range of rates: $25-$100 or so while VFP work tends to be marginally higher: in the $50-$125 range. IMHO, I think it's because of factors that have nothing to do with MS or marketing.
>
>Primarily, I think it's that VFP developers tend (not the word TEND) to be more experienced overall and it's easier to push up rates with experience regardless of toolset.
>
>Want to hear something interesting? I just got back from a tour of state government Department of Transporartation offices to install some statistical software. Not a single one of these offices (and they are pretty big for the most part) runs a VB application, yet almost half of them have FP 2.6 and VFP apps running. Why? I'm not 100% sure, but talking to systems staff at these offices, it was made clear to me that they trusted VFP apps and it seemed that it would be a *harder* sell for a company promoting a VB app there than a VFP app.
>
>
>>You say this as if it is a bad thing? You see these people as selling their souls. I see them as smart. If you know VB, and you are faced with getting $125/hour for a VB job and $80/hour for a VFP job - and making the timeframes equal and the type of work - the guy who picks the VFP job over the VB job is not only an idiot - he is a lousy business person...