I was saying that typically, a company that doesn't understand technology too well won't care what the development tool is.

Everyone is entitled to the the wrong opinion < vbg >. Anyway, that is not what you said. If that is what you meant to say, then you really must learn to choose your words more carefully.

Do you not agree that many companies that have an IT dept that includes an approved software list, will in a majority of cases, include VFP on the not approved list?

Yes. So what? If your target market is Fortune 500 companies, then learning VFP is definitely not a good place to invest your time and energy. However, for every business that employs 1000 people, there are thousands of businesses that employ 100 or less. These small to medium sized businesses need software solutions every bit as much as the Fortune 500 companies. And let us not forget that small businesses have a habit of growing up to become very large businesses. As a matter of fact, didn't Microsoft start out as a small business < s > ?

I have helped to create software for large multi-national companies as well as small businesses that employ less than 10 people. It is my personal preference to work with the small to medium sized businesses. I also prefer to use the best tool for the job when it is possible. I have deployed a couple of ASP.NET applications because I believed that .NET was the best tool for the job.

Of course, if the client insists on a specific tool, even after listening to my recommendations, I will write the application in whatever language they insist upon (with the possible exception of COBOL < g > ) as long as they can pay my hourly rate.