>Thanks Vin.
>
>I figured that inheritance would be a problem. Still, how do professional VB programmers put together an application? Slap together a bunch of Active-X components? Is there any other way of getting code reuse other than BAS modules and visual components?
>
>Thanks.
>

That's a complicated one to answer. Yes, code reuse in VB is absolutely possible, even without pure inheritance. It's all about creating and using small class (or BAS) modules to take actions, and then making those calls as necessary. And, interface inheritance helps some. And multicasting, while complicated, can really help expand GUI functionality (I wrote an article on this technique in SQL/VB/Access Advisor about a year ago: http://advisor.com/Articles.nsf/aid/MILLV03).

This site has a good overview: http://www.swynk.com/friends/hughson/VBCOMPart1.ASP

Also, see the Books section here on the UT.

One last note. I always end these posts with a bit of advice -- be patient and be open-minded. Just as FoxPro is much more powerful than non-Foxers realize, VB is much more capable a language than many VFPers give it credit. Be careful to think through what needs to be accomplished, and not just what command you are looking for... in other words, just because VB doesn't have an "AddProperty" doesn't mean that you can't persist data at run time.... you should be sure to step back and think through the goals of your app/code -- and then try to start "thinking in VB."