>>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.
>
>
>Without a native compiler, VFP is dead. The only people keeping it alive are the people who can give lip service.

I do have to disagree with you to an extent. I think VFP is the fastest thing I've had my hands on for portotyping and developing applications. Though, users have to buy powerful machines, VFP has its database side advantages for stand-alone and the views approach to clinet-server have really served a good purpose.

Developement speed is a very big issue as it also means cost.....

Kamal