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

Then why don't we all just go back to Assembler? oooooTHAT'S it!!!! machine specific code so it will run as well as it can on this one particular machine. Oh yeah, my users here would just LOVE that. Once I get around to their machine that is, which will sometime in the next millenium.

Sorry, had to get that out of the way.

However, I WOULD like to ask you a question, what would YOU suggest we use?

"You don't manage people. You manage things - people you lead" Adm. Grace Hopper
Pflugerville, between a Rock and a Weird Place