>Most of my clients rely on me to pick the right tool for the job; that's why they hire me rather than an idiot with a hammer who thinks all problems are nails. I can't remember the last time a client said "I want to hire a VFP programmer to write an application"; the standard question is "I have an application I need developed, how would you recommend doing this?"


Ed,

For once, we agree. My clients don't give a rat's a$$ if their application is written in VFP, VB, Powerbuilder, Access, Delphi, or C++. They shouldn't have to, and some might say that if the appliation is done right, they shouldn't be able to tell the difference.

I don't tell my plumber to use copper pipe vs. PVC, becuase that's not my job. I assume he knows which is the right material to use for my sink and which is right for the brewery down the street. I don't ask him, because the knowledge wouldn't do me any good anyway. I trust his expertise, which is what I'm paying for in the first place.

It's the same with applications: the customer tells the developer what thier business needs are, what the financial contraints are, and what the time frame is. It is up to the developer to choose the correct tools, write an application which meets their needs, and get the hell out. If a customer hears all sorts of doom-and-gloom about VFP, just don't tell them that you're writing the app in VFP. Saying you are using "an assortment of languages from Visual Studio" is 100% true, and for all of it's usefulness to the end user, tells them exactly what they need to know.

Bill