My experiences go both ways -- some customers don't care at all, some care a whole lot.

I've been building large transplant matching applications with VFP for a local Children's Hospital's research group for years, and I am experiencing increasing resistance from their IT department specifically because they think Foxpro is the culprit in decreased network performance, a potential security risk and unruly citizen in the network. They tell my clients that Foxpro is "certainly something we won't support -- you are on your own." As a result it is becoming harder and harder to continue this particular work -- if I didn't have the research department head's unwavering support that I've earned over the last decade and a half, I'd have to rewrite the whole Winchester Mystery House from the foundation up. Which might not be a bad idea, since by now the system sure has doors that open up to blank walls, hallways that lead nowhere, and staircases that go on endlessly but lead nowhere, like in M. Escher's paintings. The thing screams out for refactoring, but since it is in heavy daily use there is no time to stop and do that, and as long as the department head keeps her position the system will continue running despite the IT department's displeasure.

All in all, I personally see increasing resistance to VFP, especially by IT departments, and I believe that this resistance will eventually kill the language if nothing else will.

Pertti


>snip
>>My personal experience is that even when VFP was a viable Microsoft tool there was generally resistance to it that had to be overcome. Sometimes I could overcome that resistance based on price and development speed.
>>
>>Now that it is no longer a current Microsoft product, potential customers immediately want to keep away from it unless there is some extrordinary reason that it has to be used rather than current technology that is in widespread use (VFP never was). Price and development speed are no longer significantly different with VFP. Antiquated interface, lack of developer support, lack of Microsoft support, the thought of local tables (although I never store data that way), etc all work against it.
>>
>>Yes. It's dead. Bury it.
>>
>
>During the six years we distributed our VFP app we supported about 700 installations. We only ever had 1 client who asked what it was written in. When informed that it was VFP, he was not happy, but went ahead with it. He called a week later complaining about performance, blaming VFP. We were not having problems anywhere else, so we paid him a visit. Our network guy slapped a sniffer on his network, pointed out to him that he had a bad NIC flooding the network with retrys and that replacing the NIC might fix the issue. Our app then performed to spec ( and miraculously, all their other apps got a lot snappier too).