>What I find so suprising is the number of clients I deal with who 'expect' that I will be using VB as the development language to do their work in. If they require me to, I do. However, it seems that most of the time they want VB simply because they have heard of it and they still think of old xBase stuff when they hear the word FoxPro. I'm convinced that this is the failure of Microsoft to properly market Fox. That said, I agree with most of the other comments in this thread concerning changing with the times. But I also think that as the 'expert' that my clients have hired me as, it is my job to make sure they are informed as much as possible about the options they have and why VFP really can be a better choice than VB in many instances.

Personally I think it's too late... The damage is done and VFP will never
fully recover from it. VFP is an excellent tool - maybe the best for building
data centric applications. This is why I continue to use it <s> - as a developer
who has to build apps I could just not function in the environs of VB and
still be called productive.

If VFP is not renamed and repositioned I don't see this change regardless
of the merits of the product. I think the chances of that are also slim.

Most people I work for don't ask what tools I use. They need a job done
and they don't care as long as it a) gets the job done, b) is finished
on time and c) can cooperate with other applications if necessary...

Invariably when people find out that the apps I built are in VFP you
get the old 'I didn't know VFP could do this'...

+++ Rick ---