string input to CIN is missing?

[bmfstop]

Using a debugger to look at the input arguments to a CIN (string and Int32), I notice the input string is not there but the Int32 has the right value. The string is passed in as a block diagram constant, not as a front panel control. Does this matter? Would a byte array be better?

[Joel Andersen]

CINs are a pain.

Whenever possible, use a Call Library Function (CLF) instead. Things will go much smoother for you. If you have LV 7.0, there is a shipping example called "Call DLL.vi" in the \examples\dll\data passing\Call Native Code.llb. This example is an excellent resourse, and should address any issues you have with calling external routines from LabVIEW.