12-16-2006 01:40 PM
12-18-2006 04:54 AM
12-18-2006 07:36 AM
12-18-2006 09:01 AM
The ByRef parameter option indicates that the called function may want to write data back into the specified parameters themselves.
Anyway, I still need some more information to help you further. Could you paste the code or at least the signature of the VB.NET function you're calling?
Greetings,
Hans
12-18-2006 09:05 AM
12-18-2006 10:00 AM
...ahem, actually I don't see any array parameters in the code signature. But you were asking for handing over arrays?!?
Looks like some old VB ADO code has been transferred to VB.NET. The Database and Field parameters are not arrays but ADO classes or types defined somewhere else in your code, as far as I can see. They may be derived from other collection or array based classes, but I'd bet they're not.
The function you've posted simply does an evaluation of the data within a Database object using the Field object, both handed over as parameters, so their actual values must originate somewhere else in your calling LabVIEW code...
Sorry, but this takes some more investigation of the whole project to help you further.
Greetings,
Hans
12-18-2006 11:00 AM
I'm also not sure what version of LabVIEW you're running, but we did change the mapping some in 8.2 so that byref parameters of primatives (int, string, arrays) showed up correctly (i.e., you don't need to make them .NET references first).
However, if you ever do need to convert a LV primative into a .NET refnum, use To .NET Refnum.vi in <vi.lib>/platform/dotnet.llb