Warren,
Thanks for the input. Your suggestion was my first approach, however
the instrument that I am using is somewhat dated and requires that its
custom commands be compiled by a 16 bit compiler. I am assuming that
this would make it difficult to interface with labview, as the CIN source
would need to be compiled with a 32 bit compiler. Am I mistaken?
Since my posting, I have found a solution in using the g toolbox messaging
functions to send messages to my 16 bit windows application. I used the
spy program in Visual C++ to determine the proper message parameters. This
seems to do the trick. Thanks for the input,
Chris
wxfield wrote in message news:<5065000000050000002E3A0000-993342863000@exchange.ni.com>...
> Hey Chris,
>
> I thi
nk you might find it easier to just make a CIN or a DLL that
> contains the switch statement and all your code. You would pass in a
> LV Boolean that toggles either/or and it will pass back whatever data
> you like in Labview.
>
> If you drag/drop a CIN object into a labview window, you will notice
> that you can right-click on the object, and it will give you the
> option to "create a .c file.." - Before you do so, wire your intended
> inputs to the CIN and outputs. The data type will be created for you
> in the .c file when you generate the code. All that's left to do it
> cut/past your switch code and compile.
>
> Let me know if you get stuck, I'll help you out.
>
> Kindest,
> Warren