<snip>

I've been following this discussion, hearing both sides. I am a fox developer, however I also program in C, etc.

John is a bit blunt but he has made some valid points. To me the major one is use the right tool for the job at hand. I would not use VFP to do advanced statistics. However, VFP fits well in my world. Simple applications for companies that need a little more than Access, but a lot less than SQL server. Also, I spent a good deal of my time interfacing to many other products and have found VFP a good tool to do this.

I think that the person who wrote the article was a little short sighted, however we should face the facts. A lot of people do not know what kind of tool we have with VFP and therefore perceive it as exactly the same as it was in the late 80's early 90's. Therefore their comments are correct as far as they know. We should try to educate them, not abuse them.

I realize that ignorance is no excuse, however, I also saw the response from the company and they apologized quite a lot. There is a point to be made, about these things.

So saying that, let's end this thread soon and get back to work. If you want VFP to live and be a viable development tool, use it. Flaunt it, let people know. Don't hide the fox icon.. Don't complain about Microsoft... as the Nike ads say
JUST DO IT!

Just my $.02,
Mike