John,

I'm starting to think that Michel is paying JVP to bump the traffic here so Michel can sell this joint for a higher price...

"Wow! Look at how the traffic has jumped!"

<g> & < gr&rvvff MF & JVP >

Best,

DD


>>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.
>
>Of course not, but if you don't know something reasonably well, you shouldn't make pithy and insulting remarks about it. And that's exactly what frosted Jeff and why he started this thread. It's not like the guy said something technically inaccurate like "VFP doesn't support COM" in which case you correct the issue and move on ... what he said was, "You get paid for that?" when Jeff was asked what tool he used to develop in.
>
>>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.
>
>Again, this strays far from the incident Jeff reported. And if someone starts up with "VFP has a large memory footprint", then you counter with "Yes, it does, at the smaller applications level. But it consumes less OS resources (handles, GDI) and has a smaller impact than VB once you move past a certain UI object and form count."
>
>>You see JK, it is a losing argument from the outset. It is one you cannot win.
>
>Who's trying to argue? I'm just refining the point.