Dude, don't even get me started on relative competence of VB developers.

What a lot of folks don't realize is that VB has some dirty little "gotchas". Once you get past the not-so-important drivel that it's not OOP, you get into the real problems which are:

1) VB is a pig in large apps. VFP has, actually, a smaller footprint than VB in apps with 20 or more forms and a fair amount of controls.

2) VB is not swift enough to be good enterprise middleware. There's not a single VB component that couldn't be redone better in VC++ or VFP.

OTOH, not to bash VB too much, I think VBA and the adoption of standard application object models held together by VBA is the best idea to come along in a while.


>>So you've seen that, too, huh? Everytime I bring that up I get shouted down.
>
>Yes, AFAIK, there are no operational large systems here done in VB, in spite of a number of attempts - but how much to blame VB and how much to blame Tom's #2:
>
>"2.) A large supply of incompetent VB programmers."
>
>is a fair question :)