>I was discussing new projects with a client today when he asked "What's happening with Foxpro?" I know what was going through his mind, Visual Basic is in everywhere and Visual Foxpro just doesn't have a healthy profile.
>
>Why is that? VFP seems to be a fine, useful language. Why does Microsoft not push it? Is there something wrong with it? Am I charging down a dead-end street?
>
>I am not satisfied with the usual answers of "Oh VFP 6.0 or VFP 7.0 or whatever is on the drawing board", let's face it folks, Microsoft does not want VFP to be mainstream, they are killing it softly.


Visual Foxpro may be Microsoft's product, but in the end it will be the developer community that makes or breaks the product. It is not Microsoft marketing that will promote the product, it is US! Microsoft marketing will give the product credibility but we can provide the muscle by developing successful apps.

When people ask me what I think about VFP I tell them it is the best client-server database application development tool available. IF they want a language to program their VCR or make coffe beans dance on the screen, try something else. If they want a system to manage information, VFP is it. I really don't care how many people want it used, as long as there are enough to keep me employed. That's up to me!

If there is an enemy slowly killing Visual FoxPro, we have seen him, and he is us.

Bob