• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 397
  • Last Modified:

inheritance in VB

Are there inheritance features in VB like C++ or Java so that I can create subclasses that can inherit methods and properties from superclass?
1 Solution
Nope. But what do you want to do or know. Because a one word answer is not worth 100 points.

You have interfaces though in VB but no inheritence of code. Sorry.
The 'Implements' keyword will allow you to inherit the interface, but not the implementaion.
If you need inheritance in VB really badly, see this concept (grabbed NG posting)

Here's how I get VB to 'behave' like an OOP:

First, create your base class as you normally do.  I include complete code
here - this is no empty interface class.

Next, create a subclass that will 'inherit' from the base.  add the
IMPLEMENTS line in the general dec area *AND* add an instance of the base,

Implements BaseClass
Private objBaseClass as New BaseClass

Now expose the private interface of the base class as IMPLEMENTS requires.
but *also* add a public interface to match the private base class.  This
creates a 'published' version of the 'inherited' class (messy, but

Now in each *public* member add code like this:
Private Sub BaseClass_MyMethod()
   ' add this code yourself
End Sub

Yes, I'm delegating from the private class down to my local instance of the

Finally, add an additional delegation from the public interface of SubClass
down to the private interface (truly a waste of time, but needed for type

Public Sub MyMethod()
   ' add this code yourself
End Sub

You now have a subclass that has 'inherited' all the behavior of the base
class.  Any changes in code in teh base class will be reflected in the
subclass without any need to touch the sub class.

Of course you can do overrides in the sub class as needed and add new
properties and methods in the sub class to extend the base class.

Here's my key steps:
- add implements and get a local instance of the base class
- add a public interface to match the private interface
- delegate from the public interface to the private interface
- delegate from the private interface to the local instance of the base

The problem will all this is that its so danged tedious (and kludgy).  I
wrote myself an addin that does all this work for me, tho.  Now I just build
the base class, call the addin and tell it to build my subclasses.

Michael C. Amundsen, MCP, MVP

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 As told by many above, in VB there is no code inheritance. yes u can have interface inheritace thru the IMPLEMENTS keword
u can inherit the interfaces and write ur code there
kimsoyAuthor Commented:
Are there any downsides that I have to keep in mind?
kimsoyAuthor Commented:
I forgot to thank ameba, you have saved a lot of time and efforts. Thanks again...
kimsoy, if your SuperClass *definition* change, you are in trouble: Too many changes in your code, re-delegating code again...
You can simplify things, if you throw Implements and all its code, and use *only* instance of the base class, but you will loose type checking.
Some experts think inheritance is more trouble than benefits.
kimsoyAuthor Commented:
Here is the other way to do ingeritance that I got from other VB web site.  I didn't try this example yet, but it makes sence (I think...).

      'Class : clsStudent
      ' Contains a reference to a Person Object

      'private member variables
      Private oPerson as clsPerson
      Private iGrade as Integer

      Public Sub Create ( )
      'load this object and create the person object

           Set oPerson = New clsPerson

      End Sub

      Public Property Let Name ( sNewName as String)
      'set the person objects Name Property

           oPerson.Name = sNewName

      End Property

      Public Property Get Name ( ) as String
      'retreive the person objects Name Property

           Name = oPerson.Name

      End Property

How is it different from the answer I was given?
Which way is better (less trouble)?
Yes, this is less trouble (without Implements).
I think, you should remove "Create" method and use:

Private Sub Class_Initialize()
    Set oPerson = New clsPerson
End Sub

Private Sub Class_Terminate()
    Set oPerson = Nothing
End Sub

Well, someone can say this is not Inheritance, but Delegating.

Implements can help if you have a Method that expects BaseClass as argument:

Public Function IsRetired(objItem as clsPerson) As Boolean
    If Left$(objItem.Name, 3) = "em." Then
        IsRetired = True
    End If
End Sub

Without Implements, this will produce type-mismatch error:
Set objStudent = New clsStudent
x = IsRetired(objStudent)

By adding Implements you can avoid this error.

But this works only one level deep: If you have clsEEStudent which implements clsStudent, you will not be able to use IsRetired method - clsEEStudent doesn't have Implements clsPerson line in the module :(

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now