>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.


Chris (and others)

I think most of you are missing the point. MS is now headed towards an integrated development invironment. There will not be One is better then the other in the future. It will be which language/engine is better for the app your currently working on. It is rumored VFP will take on the role as the front end for the (also rumored) SQL Server Lite (see the VFUG August Newsletter for more details). Why do you think ActiveX and OLE Servers and 3 Tier deign are being touted so heavily now? Also see my article in the September VFUG newsletter on this (not yet released -- early September).

Tom