Chris,

You ask a question, then you answer it. Seems like your mind is made up.

MS has finally (see editorial of August 1997 FoxPro Advisor) made a STRONG statement in support of VFP. VFP *has* become a part of the new integrated development facility. VFP 6. *IS* in development. DEVCON *IS* scheduled as ever before, perhaps to have more attnedees than ever.

Yes, relatively speaking there appears to be oodles more VB programmers/users than VFP. But I gotta believe that VFP is FAR from being a money loser for MS.

If you wanna believe that MS is killing VFP, nothing I or anybody else says is going to change your mind. It's kind of like suspecting that your spouse is fooling around on you, even though he/she is not - you are sure in your head that it *IS* happening!

Finally, it sure is both a crude and un-business-like way to "kill" something, if that's their (MS') real objective. I just don't think they would go about it in the way you suggest.

regards,
Jim N

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