why a VI has a broken arrow when I open it when labview is open but becomes executable when it is opened by double clicking

[USC_gamecock]

I have a VI with some subVIs from a dynamic link library. When I open the VI using "open" or "open VI" in labVIEW, the VI is broken. In the error list,it saids one or all the subVIs from the dynamic link library are not executable. However, if I exit labview and open the same VI by double clicking it, it becomes executable without any change being made. Sometimes I can fix the broken arrow by configuring the "call library function node" in the subVI and saving it. But when I open the VI again, the same problem and error message appear. I am using labVIEW 6.1 for the top level VI and those subVIs from the dynamic link library could be developed in a different version of labVIEW. Is this the cause of the problem? Another possible reason I can think of is that somebody installed another application developed in labVIEW on the same computer. Is it possible that some settings were modified during the installation that cause this problem to occur? I am suspecting this because I first notice this problem after the installation of the other application.

[tbob]

In your block diagram, click on Browse menu - Show VI Hierarchy. Make sure full vi pathnames are shown (in Hierarchy window, click View - Full VI path in label). See if any subvi's have a different path when you open your vi one way versus another. This might give you a clue to what is going on.

[USC_gamecock]

I checked the path for all the subVIs when the top level VI was opened in labVIEW or launched by double clicking. Their paths seemed to be the same either way.

[tbob]

Since the problem started ocurring after installing another application, I would suspect something with that last installation. Without knowing more about the installations, I would not be able to help much. Did the other installation perhaps install another DLL of the same name? Try uninstalling the last app to see if the problem goes away.

[KileenC]

The behavior you are witnessing can happen sometimes when you have multiple versions of LabVIEW installed on your computer. With dynamically linked libraries, make sure that when you configure the Call Library Function Node, you give it an absolute path to the DLL. This will ensure that the vi is looking in the proper directory for that DLL. Then, mass compile your VI (Tools >> Advanced >> Mass Compile). This should hopefully then recursively go through your top-level vi and save all the necessary information.

Best of luck!

Kileen