>And then the need for bail out services <bg>

LOL (although VFP and VB6 developers are probably not LOLling or ROFLing -- more like "rolfing" -- getting a soothing deep tissue massage to ease tension...)

>
>>And then the jobs follow... :o)
>>
>>
>>>>>PMFJI, without taking any sides, I have actually seen higher than usual rates which I
>>>>>attribute to companies finding it harder to find VFP developers these days. Lack of
>>>>>developers means I can ask and get a higher rate for Fox projects that companies are
>>>>>forced to maintain.
>>>>>
>>>>
>>>>I concur. It appears companies are having a tougher time finding *competent* VFP developers to maintain their systems (note I said MAINTAIN).
>>>>
>>>>I've found almost no new development opportunities for VFP based applications.
>>>>
>>>>I can develop VFP based solutions for my customers as long as I don't stress the VFP part, but I try very hard not to develop anything new in VFP bacause it is doing the customer a disservice unless the application lifespan is known to be very short. If a customer has any expectation to use an application more than a year or 2 I will not do it in VFP.
>>>
>>>
>>>I also maintain some VFP apps, and the money's good.
>>>
>>>I saw one blogger who said that VFP is not dead, but Done. It's a nice sentiment, but I do believe that VFP is
>>>on the way out.
>>>
>>>Still, I'm moving to C#, not because of all the press about it, but because MS says it's the
>>>next best thing. And when MS speaks, companies tend to listen.