>My question is, has anyone had experience's with these self-acclaimed VB experts and what did you learn from your experience?
Some of the ones I met seem to be hiding the fact that they really don't what they're doing when it comes to integrated development or real-time transaction processes. I know for a fact that a lot of BIG companies are powered by Fox (DOS to VFP 6), but their systems people don't want to admit it. Isn't there some old saying (paraphrased) that goes: The weak gang together aginst the strong. Folks, VFP developers just need to be proud (not shy) about the fact they work with VFP. The weak are taking advantage of our politeness.
Some VBers still advocate 'user errors' as an implementation problem (they dont have that big VFP PEM) and require endusers to accept limited or cumbersome functionality. They also use the word 'Robust' alot. Understand, most VB projects are built around viewing data, not processing it.

I learned that the department heads backing the strict VBers get into trouble when projects don't get delivered or the delivered project comes with limited service and a bunch of user rules.

The big differenc between VB and VFP guys - most VBers are corporate bench 'programmers', loose one, another can slide in, while; alot of VFPer's are independent developers.

Employment agencies like VB because projects take forever. They make money on it. MS likes VB cause they'll get additional licensing for SQL. FoxPro has a cursor, has Rushmore and recordpointers.

RANT OFF:)