CVI dll crashes when it uses RefNum var passed in from other CVI code or from LV 2009. Why?

[ctakac]

How would any of you configure the LVRefNum parameter for the file in the Call Library Function?  I have it set up as "Adapt to Type" and "Pointers to handles"

[rolfk]

Sounds good to me, although the extra setting about how to pass handles has no meaning for it, since a LVRefNum is simply a skalar number and not a handle.

I wonder if CVI somehow gets into trouble about what to link for LVRefNumToFD() and friends. CVI has deep down some LabVIEW heritages, since NI used the LabVIEW 3 low level code to get a head start in creating CVI. It could be that some of these functions get exported by CVI libraries too. To check this you could try to remove the labview.lib file from the project settings and see what type of missing link symbols you get. If these functions are under the reported missing link symbols this should not be the problem.

Rolf Kalbermatter