> I just don't want to debug it...... i think u mixed up with the visual c++
> debugger.... and the debugger i mentioned in my post....
>
> the debugger i'm using is written by my company...and we use it for some
> testing on our cards.... and now we want to test more than one card at a
> time...so we planned to use labview...
>
> so to do this i made a dll using borland c++ which contains all the routines
> to commuincate with the card.... and the debugger(which we wrote) uses it as
> well....but it can only do one card at a time...
> and there is no automation...
>
> so...i wanted to know in wat way should i use labview....so that i can avoid
> using that debugger...
>
To answer the earlier question about the dialog and creating the .c file.
Use the dialog to configure what and how you need to transfer between
the LV diagram and the DLL function. You do not need to use the Create
..c file menu item unless you want to. It is for those starting from
scratch and deciding from LV what they are passing in.
The dialog for the parameter configuration is needed mostly because
a C header file, a .h file, doesn't have enough information to
construct a call from LV. What type of string and array does the DLL
expect? If the DLL were given an automation interface and made into
an ActiveX server, then this wouldn't be necessary and you could use
the invoke node. The parameters would automatically be configured,
because in the process of making the automation interface, you would
more accurately specify the way parameters are passed.
Anyway, I hope that you have everything working now.
Greg McKaskle