Cannot change library path or name when configuring a library call function

[SethS]

I cannot change the library path or name when configuring a library call.  I browse to the new location, click OK.  The new path appears  in the box.  I click OK to dismiss the configuration.  Then I re-open the configuration and the old path has magically appeared.  I wouldn;t care but I get a fatal error whenever I execute the call.  (Another VI with the same call but to a different library works fine.  So I am trying to get the failing call to use the one that works.)

[Starla_T.]

Hi SethS!

Try configuring the parameters before you select ok.   You  can also try placing a new Call Library Function Node on the block diagram from the palette and deleting the old one that doesn't seem to working.   

Hope this helps!

Starla T.

[SethS]

The whole vi is configured when I try to change the path.

I have tried starting with a new library call and configuring it.  Again the path changes to the old one. It's like the vi "knows" the path and it's not changeable with the configure screen.

[Starla_T.]

Hi SethS!

I've never seen that kind of behavior before.  What version of LabVIEW are you using?   What library are you trying to call from?  Can you post the code?

--Starla T.

[SethS]

I am using version 7.1

It turns out that everything works fine in LV 2010 but the customer doesn't have that rev.

I am remotely debugging this using GoToMeeting.  Sounds weird, but I fell into that.  It works fine, I have a screen which looks exactly like the screen in the customers site.  I can do everything, albeit with a little time drag.  The thing is, I e-mailed the VI from his site to mine so that I could send it to you.  But it works fine here.  So the question is what could be different there that would cause this?

The main problem that I am trying to solve is that when I run the VI, I get a message

"Labview:  An exception occurred within the external code called by the Call Library Node.  This might have corrupted Labview's memory. Save any work to a new location and restart Labview"

If I set the Library Node on my machine to the correct function, it runs without error.  It seems, however, to start with a different function and then I get the same error.  I would think that if there is a parameter mismatch that the library would return an error status, but this appears not to be the case.  (I did not write the library, HP (Agilent) did)  The function is correct at the customer's machine.

[Starla_T.]

Hi SethS,

Was the original code written in LabVIEW 7.1 or saved for previous versions from a newer version?  You can narrow down the source of this error by installing a free trial version of LabVIEW 2010 on the customer's PC.   If code runs on 2010 on the customer's PC, you'll know it is an issue related to LabVIEW 7.   If the code still doesn't run, then it is most likely an issue with the customer's setup.   Also, I've read some documentation that suggests calling external code in LabVIEW 7.1 and earlier is different than calling a library function in newer versions.   I was able to find an old help file on Using External Code in LabVIEW 7.1 and 7.0. I would read through this file and try to determine what is different.

Hope this helps!

Starla T.