I know what you mean. My coporate IT manager even asked me "why are you using old FoxPro, instead of MS-SQL or Oracle, or even ACCESS?"
First, I replied is "because Fox does the job, and costs a lot less."

But that exchange is an indication that us Foxpro developers should be discussing with our clients the matter of "solutions" instead of discussing a specific language that they may have heard of or may not. You no doubt note that Microsoft and others now talk in terms of Solutions.


>>>I had a conversation with my acquaintance, and when I mentioned, I work with VFP, she told: "Such an old product..." with obvious disrespect. I had the similar experience in the past too. Sometimes I even ashamed to admit I work with VFP. Do you know the reason of such attitude from outside of VFP world?
>>>
>>>Thanks in advance.
>>
>>Nayda,
>>
>>I went to a job fair in Chicago a few weeks ago and faced the same attitude. I don't know how many times I was asked, "FoxPro! Is that still around?". I didn't run across one employer or agency booth who was open to FoxPro. I came back wondering if I should bite the bullet and start learning a new language. Not because I want out of FoxPro, but because it's getting harder and harder for me to find FoxPro projects.
>>
>>Cathy
>
>Cathy,
>
>The question is: can we (all VFP lovers) do something about it or all of us should choose another language? The community here is great, but outside ot this small world we all face this attitude from time to time. Looks like we have to struggle to our right to use this programming language. Why is that? :(((