>If they know the answers, nothing is lost. If they don't, a lot is gained.

But that smacks in the face of your proposition. Your goal in this little confrontation was to "1 up" the VB guy. You look pretty stupid standing there, in an accusatory fashion when the guy answers the questions.

The bottom line is that many in the VFP community have this huge chip on their shoulder. They believe/think that VFP has some distinct advantage over VB and that VB is somehow inferior to VFP.

If you are building single/2-tier apps, I suppose VFP has an advantage. Unless you have been asleep for the past 2 years, it is quite evident that MS does not care about single/2-tier apps. In fact, if MS could control things, these type of apps would go the way of 16-bit windows...

Even with single/2-tier apps, I don't think VFP has a distinct advantage. Then again, I know both tools. Most folks in the VFP community know 1 tool. Of course to them, VFP will have an advantage. From my vantage point however, on the whole, I see no advantage. Specific issues, yes. And each has advantages. On the whole, it all balances out...

>
Because if you can prove that the person is limited to a specific topic in terms of general knowledge, it devalues anything derrogatory said about VFP which is, in itself, outside the sibject matter. It's psychological.
<

Wacked logic. Let's say I have limited knowledge about the specifics of SQL Server, but I know Access/Jet Cold. DOes that really devalue anything I say about VFP? When we evaluate tools, do we take the time to become experts in the tools we are evaluating? Of course not. That would be highly impractical.

If some guy says VFP sucks because it has a huge memory footprint, what are you going to say? The guy may know nothing else about VFP. Does that devalue what he said? Not really. VFP has a big memory footprint. It is a known fact. Does VFP suck? To him it does. That is his opinion and he is entitled to it.

You see JK, it is a losing argument from the outset. It is one you cannot win.