Error when accessing low level objects and converting variant to refnum Type

[arsa]

Hope someone can give a clue....

I'm using a dll, but it only has one creatable object, and I need to call two non-creatable objects.
When the method to return the new reference is called, an error occured ("Member not found.
in My.vi").
The weird thing is that when I wired the new reference, I'm able to see the new methods and properties expected of the new object.
Should I ignore this error???

Also, does anyone know, How can I convert a variant to a ActiveX refnum??? because, when I use the To G type Lib, if a refnum type is wired, it's like this type is not supported, but the list states otherwise.

Thank you in advance for any clue you can give me!!!

[JRA]

Since I do not know what type of ActiveX object you are calling, I do not know about the error you are seeing. However, since everything seems to be working after that, I would assume it's okay. Now, you can convert a variant to an ActiveX refnum, but how you do this depends upon what type of refnum you need. Use the Variant to Data.vi to convert your variant type to a refnum by wiring in an ActiveX refnum to the "type" input. You will first need to determine what type of ActiveX refnum it is (Automation, Control, etc) and then wire that wire type into this VI.

[arsa]

Thanks for your answer.
I'm using a dll made in Visual Basic to configure an external hardware. It's not commercial.

However I just found out that an object's properties are not the same, when I call the same dll in Visual Basic for instance.
In Visual Basic, I call the object and it has two properties, however, when I call the same dll in LabView, the same object has only one property, and the other property missing appears as method.

I guess that propably this is the first reason to get the error. (member not found)
And since the dll was made in Visual Basic, and I'm not an expert, I do not know how this can happen. Or if it's a LV error when interpreting the dll.

Any clue???