Thanks for the answer, but this is exactly what I have been trying to do
without any luck.
The problem as I see it is that it is an out-of-proc COM component. I can
easily invoke methods on in-proc COM components, that is components in a DLL
file, but not with out-of-proc components (which is components in an EXE
file).
A solution would be to implement an in-proc COM component that calls my
out-of-proc component, and then include that into Labview. But this I would
like to avoid.
I hope I can get some other suggestions from this news group.
Thank you in advance
Jihad Haddad
"Greg McKaskle" wrote in message
news:3CC18B65.4060300@austin.rr.com...
> > I have an out-of-proc COM Component (an exe file), and want to have
access
>
> to its interfaces through LabView. This seems impossible, even though I
have
> > seen that it is possible to access interfaces from an in-proc COM
component
> > (a DLL file).
> > Is there any way in which I can do that.
> >
> > I have the feeling that the COM component can be accessed, if just I can
get
> > labview to see the interfaces. Is there any way to specify the TLB file
of
> > my COM component, or insert the interfaces manually?
> >
>
>
> Try dropping an Automation Open node, right click and browse for the TLB
> or the class definition in the list of registered classes. From there
> you will want to use the invoke node to call methods and the property
> node to read/write properties. The ActiveX nodes can deal with many COM
> interfaces, but they restrict the datatypes to those covered by
automation.
>
> Greg McKaskle
>