>When VFP3 came out he refused to use it since it was a new tool.

FoxPro has been there since 1986. The OOP feature was the major change in Visual FoxPro but the same goes with the first Windows version, the addition of the power tools and Rushmore technology with prior versions, etc.

>Also, he received a BAD opinion from a well known consulting group.
>He asked : "What is the positioning of Microsoft Visual Foxpro 3.0 ?"
>They answered : "... The product does include limited multi-user capabilities ... The underlying data management technology is simply not robust enough for any application serious enough to require multi-user support ... We would urge you to consider appropriate client/server development tools"

What is the name of this consulting group? I thought that the "Just for laugh" festival was finished but it doesn't seem like it.

>Now, I am trying to convince him to use VFP5 for a new application.
>Again, he consulted the same group and was told that VFP is going to be discontinued after 5.0.

Is this consulting group a competitor of Microsoft related to a database package? This would have explained this MORE THAN STUPID comment.

>Sure - we have all heard those rumors for quit a while.

The same goes with most of all other packages, rumors if there was.

>HELP ME IF YOU CAN -- I am trying to gather as much information as possible to convince him that his consultant is wrong.

Hey, the Universal Thread is driven by Visual FoxPro 5. :)