Include HPVEE-Files

[CHZ]

Hello,
I've been working with LabVIEW 5.0(Evaluation) for 3 weeks.
My colleagues create programs with HPVEE.

My question: How can I include such HPVEE-Files in my VI's?

I haven't found anything about that in the examples!

Thank's CHZ

[Kevin_work]

CHZ wrote:

> Hello,
> I've been working with LabVIEW 5.0(Evaluation) for 3 weeks.
> My colleagues create programs with HPVEE.
>
> My question: How can I include such HPVEE-Files in my VI's?
>
> I haven't found anything about that in the examples!
>
> Thank's CHZ

Why would you want to ?? Just kidding
Unless there is a way to make the HP-VEE files
into a dll (assuming windows) then I dont think
you can.
Kevin Kent

[CraigGraham]

> Why would you want to ?? Just kidding
> Unless there is a way to make the HP-VEE files
> into a dll (assuming windows) then I dont think
> you can.

DLLs aren't the only way of integration. I've never played with HP-VEE, but
if it has the ability to communicate with another application via TCP, DDE,
ActiveX or whatever, then it'd be possible to integrate applications written
by different people in the different environments- provided of course that
there's the necessary level of co-ordination and it's actually worth taking
the time for everyone to become proficient at it!

[Greg_McKaskle2]

> I've been working with LabVIEW 5.0(Evaluation) for 3 weeks.
> My colleagues create programs with HPVEE.
>
> My question: How can I include such HPVEE-Files in my VI's?
>
> I haven't found anything about that in the examples!

You won't find anything specific to VEE, but you will find that
you can call EXEs, or execute any command line; so I know that
at least that much will work. If the EXE exports an automation
interface, an ActiveX interface, then you can control it from LV.
Similarly, LV can communicate to DDE servers and TCP servers.
Finally, there is always file I/O. It is the slowest, but when
all else fails, you can pass information between almost any two
programs by passing it through a file, and using the existence
or disappearance of a file to signal e
vents between programs.

Greg McKaskle