Link to home
Start Free TrialLog in
Avatar of BROOKLYN1950
BROOKLYN1950Flag for United States of America

asked on

Exposing .Net Methods To VBA (COM)

I am currently in the process of extending my Excel VBA project using VB.Net and Visual Studio. I’ve created a working DLL, made it COM visible and registered, and referenced it from my Excel file.
      In my DLL, I have created a few classes (each with its own interface and explicit GUID to prevent errors caused by adding/removing methods/properties). I have successfully used these classes in VBA in this way:

Dim abc As New MyClass
abc.MyMethod

Open in new window


      The problem is that I have a few subs that I am trying to use that aren’t part of any class. These are in a module call “Misc”, as shown below:

Public Module Misc
	Public Sub MySub()
		…
	End Sub
End Module

Open in new window


      I want to be able to call these from VBA, either by just saying:
Call MySub

Open in new window

Or
Call MyNamespace.MySub

Open in new window

     But when I try to call the sub, it can’t find it and I get “sub or function not defined”.
The only way I’ve been able to access the sub is to write a class and interface that simply calls that sub, but that seems like a lot of work just to call one sub, plus I also have to create a new instance of the class in VBA before I can call the sub, adding an extra line of code.
      Is there any way around this?
Avatar of Nasir Razzaq
Nasir Razzaq
Flag of United Kingdom of Great Britain and Northern Ireland image

Does following work?

Call Misc.MySub
There is an option. Change the module to NonInheritable (static) class and method as Shared (static) method. So that it could be called as Module.Method without more code changes.

http://stackoverflow.com/questions/436605/vb-net-how-to-reference-vb-net-module


HTH.
Avatar of BROOKLYN1950

ASKER

I tried both your suggestions. I can't believe I didn't think of CodeCruiser's suggestion, but just as well I guess, 'cause unfortunately it doesn't work. As for EaswaranP's suggestion, I changed:

Public Module Misc

      Public Sub MySub

      ...

Open in new window

to

Public NotInheritable Class Misc

      Public Shared Sub MySub

      ...

Open in new window


      Unfortunately this didn't work either. I could not call the sub directly, no mater how explicitly I wrote it or how I used the "Call" statement. I could get the module (or class as it now is) to show up by saying:
Dim abc as MyNamespace.Misc

Open in new window

But when I tried:
Dim abc as MyNamespace.Misc
abc.MySub

Open in new window

I got an "object reference not set to instance of an object" error.

So no solution yet, but hopefully we're getting close.
You no need to declare using Dim. Just call the method as MyNamespace.Misc whenever you required. Thats it.
I tried that, as I said in my last reply,
I could not call the sub directly, no mater how explicitly I wrote it or how I used the "Call" statement.

I tried all of the below:
MySub
Misc.MySub
MyNamespace.Misc.MySub

Open in new window

And I also tried each of those prefixed with the "Call" statement (though I don't  think that would make a difference).
ASKER CERTIFIED SOLUTION
Avatar of BROOKLYN1950
BROOKLYN1950
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I figured out my own solution as explained in the answer