At 3:16 PM +0100 4/14/04, Craig Graham wrote:
...When looking at things that I've downloaded or have been sent
through email,
I sometimes get a dialog popping up warning me that certain files were
loaded from a different path than they were expected to be at. I've never
bothered looking into it bu
Paul F. Sullivan wrote:
> While LabVIEW is looking for a subVI, it displays the path where it
> expected to find it. On slower computers, one could abort the search
> before a substitute was found and read the expected location. With
> the increases in computer speed, you'll have to temporarily mo
Thanks a lot!
For anyone interested: It turns out that the sub-VIs that were loaded, resided in
another version of my application. Oops! After a reorganization of our group's
folders, LV could not find the sub-VIs on the supposed location and therefore started
to look in its search paths. Sinc
Andreas,
You wrote:
...I'm very curious but can't figure out a way to see what copy of
"Out Port.vi" was loaded the last time my top VI was saved, since
both copies I know of, seem to generate a change (*) in my top VI.
So, I'm wondering if there is a way to look inside a VI and see the
subVI
Hi,
I'm having a problem with a VI that calls a "Out Port.vi". Labview loads it from
C:\PROGRAM\National Instruments\LabVIEW 6\vi.lib\platform\system.llb
... instead of taking the one inside
\..\Common\AccessHW_LV5.llb
In "Current Changes" of my top-VI, it says "Name or location of VIs i
