How can I use an activeX component that has no creatable objects

[RainerH]

I have got an activeX component that I want to use with LabVIEW. When I want to access that activeX component via LabVIEW I see no creatable objects from that component. If I select one of the non creatable objects, everything seems to be fine and I can build my application. I can see all properties and methods of the object as expected. But when I start the application it fails with error 3005 saying 'object specified is not creatable...'. Does anyone know a solution for this problem?

Thanks

Rainer

[Scott_R]

Hello Ranier,

Are you experiencing this problem on the development computer, or on another computer that you are installing the built application to? Also, is the code executing properly before you build the application?

If you are experiencing it on your development machine, when you are selecting your ActiveX object, be sure to check the box �Show Creatable Objects Only.� Then add the object and try running your code. If it runs successfully, then build the application and execute it.

If the error is occurring on a different computer that you are installing the executable to, be sure that you have installed the drivers for that ActiveX object onto the system. Simply including them in the LabVIEW installer will not work. For more information about i
nstalling ActiveX controls, take a look at:

How Do I Manually Register Type Libraries, ActiveX Controls, and ActiveX Servers?
http://digital.ni.com/public.nsf/websearch/4F811A9B23F1D46E862566F700615B7A?OpenDocument

Let me know if you have any additional questions on this issue.

Scott Romine
National Instruments

[dan13]

Scott,
I am working with COM objects that were created by a 3rd party. Some of the objects they provide are creatable, some are not. What makes a COM object such that it is not creatable? Is this a Labview issue or Microsoft Windows issue? Is there a way I can make the object creatable? If there is nothing that I can do, what do I tell the 3rd party so that they can fix the problem?

Thank you,
Dan

[beetle]

Did you ever resolve your problem?

I am having exactly the same problem. I want to use labview 7.0 to control a 3rd party's application (which controls a lab instrument). I can see all the methods and properties I need, but only if I uncheck "show creatable objects only" on the relevant type library.

I have a working visual basic (as an xls macro) example of how to control the 3rd party application and it uses the non-creatable objects quite happily.

But in the VB example VB first uses GetObject to connect to a running instance of the 3rd party's application using GetObject. As I understand it, this checks the Running Object Table (ROT) to return an interface pointer.

"COMNAME" in the GetObject (, COMNAME) used in the VB application I can see listed in the Windows registry, but cannot find it (and I have looked!) anywhere in the "select object from type library" navigation dialog window.

I think it is because they are dependant objects, but how to I generate an automation refnum for them if I can't find the higher level object? Perhaps I should use CINs?

[beetle]

I want to use labview 7.0 to control a 3rd party's application (which controls a lab instrument). I can see all the methods and properties I need, but only if I use an object I can see when I uncheck "show creatable objects only" on the relevant type library.

I have a working visual basic (as an xls macro) example of how to control the 3rd party application and it uses the non-creatable objects quite happily.

But in the VB example VB first uses GetObject to connect to a running instance of the 3rd party's application. As I understand it, this checks the Running Object Table (ROT) to return an interface pointer.

The "COMNAME" in the VB example "GetObject (, COMNAME)" I can see listed in the Windows registry, but cannot find it (and I have looked!) anywhere in the "select object from type library" navigation dialog window.

I think it is because they are dependant objects, but how do I generate an automation refnum for them if I can't find the higher level object? Perhaps I should use CINs?