Type mismatch when initializing a COM object

Question

I have an Excel VBA module calling a C# COM dll.

Sometimes, I get a type mismatch when I step through the debugger in VBA, when I initialize a COM object as follows.

If (IsEmpty(cm)) Then
    Set cm = CreateObject("aimd.CMAdaptor")
End If

I can add a breakpoint in the VBA and add a watch to the cm variable, and see the type doesn't match what I instantiated. The type is for a property inside the object I'm trying to create. The object pointed to was clearly created by my "aimd.CMAdaptor" object I instantiated, I just don't get the root object I specify, only the child.

Since this is a COM object, I'm wondering if my updates could be using mismatched regasm data or something that causes it to look for the object in the wrong place. I am constantly rebuilding it for debugging, and adding it to an installer that calls regasm as a build action.

tbischel · Accepted Answer · 2010-12-03 00:09:15Z

1

turned out to be a dumb mistake... I was copying the attributes that allow you to select the name of a class as seen on the VBA side...

[ProgId("aimd.CMAdaptor")]

this was located in two different classes. Apparently, is no complaint when you do this. I'm not sure why it picked one over the other, but after updating the incorrect attribute, everything works fine.

answered Dec 3, 2010 at 0:09

tbischel

6,50712 gold badges54 silver badges75 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Type mismatch when initializing a COM object

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related