>VB's objects are based on the Component Object Model (or COM). There is no parent/child relationship between objects. Visual Basic is also not a true Object Oriented language.
>
>There is really no such thing as subclassing an object in VB. What you do is implement interfaces on an object. This is called Interface Polymorphism. Once you create the objects interfaces, you then supply the code to implement whatever the task is.
>
>That's a quick snapshot of some differences.
>
>To answer your question, no, it's not a bug. You are trying to do something with VB that it doesn't do.

This is what I was afraid of. If we can't build classes of objects with level of classes, it might be difficult to do RAD and have to redo the same things from application to application. Is this why there is no RAD tool for VB?