>When it comes to having a language professional (Interpreter) they specialize in one language but also know others. Take any of the latin rooted languages. It's not to hard for them to switch, now look at how close VFP is to VB. Why are there som many though nuts to crack? Were we issued cement hard hats?
>
>Or is it the conservative nature of Americans? Travel all over the globe and people speak numerous dialects and languages. I can only speak for USA attitudes here but if a tourist from any other country comes to visit they better know ENGLISH. And travel to the south they better know some "bubba speak" ie. redneck.
>
>__Stephen

You raise some good questions. I think a lot of companies are moving toward standardization, and many managers feel that VFP does not fit well in the Microsoft suite of development tools. The "foxpro is dead" rumors did a lot to reinforce that attitude. I worked with a company called MINISOFT to develop and ODBC driver to work with VFP and Image/SQL on the HP 3000. The programmers at MINISOFT constantly complained that VFP did not mesh well with the VB standards, and that develping the driver to work with both products was very difficult because Visual Foxpro was based on older technology. The VFP kernel is very old. It is fast, reliable and old. For that reason it does not fit well with the other development products. As a pure local database engine it has no rival; in the corporate client/server environment its role has become rather muddy. And there you have it...