LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

labview 7 subvi's loaded from other sources

I upgraded to lv7 and am having trouble running some programs. I get all kinds of warnings during startup that say sub vi... at ... was not found sub vi... was loaded from ...
Then when I run the program it comes up with an error message that I trace to a "new report vi" and inside it has a sub vi "word find application". Inside there is a function "current vi's path". When I install a probe it shows a different path than the vi that I am actually running?
0 Kudos
Message 1 of 12
(3,503 Views)
If you click on Browse -> Show VI Hierarchy and then View -> Full VI Path in Label, you can see all sub vi's and their paths. Since you just upgraded to LV7, I would guess that some of the sub vi's are coming from previous version of LV. Did you have Report Genreation Tools in the old version, but did not install in LV7? The message about sub vi was not found at ... was loaded from... means that the sub vi was not found where it was expected to be (from that last time you ran the vi in older LV version). But LV searched and found the sub vi at a different location. When upgrading, the sub vi's under an old directory, like LabVIEW6.1, might not be there anymore, and the vi is now found under LabVIEW 7.0 directory. In this case, the message is valid and there
is nothing to worry about. Save your main vi so that the new paths to sub vi's will be established and saved. In some cases, you may have to manually replace sub vi's in old paths with the same vi in a newer LV7 path. Once you have substituted all sub vi's with the ones from the right path, save your main vi and all sub vi's.
- tbob

Inventor of the WORM Global
0 Kudos
Message 2 of 12
(3,503 Views)
Thanks,
What I have been doing is search through the VI Hierarchy and findin all the sub vi's with all the wrong paths (many) then opening them. I then do a "save-as" with the correct path. This seems to work so far. It just seems so convoluted for an "upgrade".
Thanks again for all the help
Jim
0 Kudos
Message 3 of 12
(3,503 Views)
I spoke too soon.
I did this for one main vi and it worked. I opened another main vi and found a similar problem. I used my fix and it worked also. However, I went back to the first main vi and found the had reverted back. Between the two main vi's I seem to be "chasing my tail". I have tried saving the subvi's everywhich way but they only work for the current main vi that I have open. I switch back to the other main vi and get warnings when I open and "save-subvi" questions when I close.
0 Kudos
Message 4 of 12
(3,503 Views)
Hello Jim,

There is an extremely useful KnowledgeBase (2CKGQ6G4) called, "How Does LabVIEW Save Path Information for SubVIs?" on our website at www.ni.com/support that goes into great detail explaining how LabVIEW saves path information for subVIs. Here is a direct link to the page:

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/3e58fdcf8744f86d86256aaf0078274c?OpenDocument

I hope that this will be sufficient. Write back if there is anything that is unclear. Take care and good luck!

Aaron B.
National Instruments
0 Kudos
Message 5 of 12
(3,503 Views)
Hi,

Sounds like you need to reinstall the report generation toolkit for the new
version.

Regards,

Wiebe.


"JimN" wrote in message
news:5065000000080000002FC70000-1079395200000@exchange.ni.com...
> I upgraded to lv7 and am having trouble running some programs. I get
> all kinds of warnings during startup that say sub vi... at ... was not
> found sub vi... was loaded from ...
> Then when I run the program it comes up with an error message that I
> trace to a "new report vi" and inside it has a sub vi "word find
> application". Inside there is a function "current vi's path". When I
> install a probe it shows a different path than the vi that I am
> actually running?
0 Kudos
Message 6 of 12
(3,503 Views)
I've tried and it just asks, uninstall or repair. I have done both. The last time I uninstalled and reinstalled but I still had to move numerous files to the 7.0 folder. I'm think I moved all I could locate. Something about it that even after I uninstall it still seeks out the 6.1 folder to install into.
Jim
0 Kudos
Message 7 of 12
(3,503 Views)
Jim,

You need all the files and the directory itself called "data". This
directory has some dynamic VI's in it, that don't give errors when the
program is loaded, but do when the program starts if they are missing. The
"data" directory might be there, because the standard report generation VI's
could use it (not sure though).

Regards,

Wiebe.


"JimN" wrote in message
news:506500000005000000AF6F0100-1079395200000@exchange.ni.com...
> I've tried and it just asks, uninstall or repair. I have done both.
> The last time I uninstalled and reinstalled but I still had to move
> numerous files to the 7.0 folder. I'm think I moved all I could
> locate. Something about it that even after I uninstall it still seeks
> out the 6.1 folder to
install into.
> Jim
0 Kudos
Message 8 of 12
(3,503 Views)
Hello Jim,

When you install the Report Generation Toolkit, you are prompted to include a path at the very beginning of the installation process. Make sure that you are installing the toolkit in your LabVIEW 7.0 folder and not the LabVIEW 6.1 folder. Take care and good luck!

Aaron B.
National Instruments
0 Kudos
Message 9 of 12
(3,503 Views)
Hi,

The data directory only applies to executables (they do need a data
directory with the same files in it).

The files I mend are in vi.lib/addons/_office. But if you reinstall it like
Aaron sugested, it isn't necessary.

Regards,

Wiebe.


"Wiebe@CARYA" wrote in message
news:4063ec88$1@newsgroups....
> Jim,
>
> You need all the files and the directory itself called "data". This
> directory has some dynamic VI's in it, that don't give errors when the
> program is loaded, but do when the program starts if they are missing. The
> "data" directory might be there, because the standard report generation
VI's
> could use it (not sure though).
>
> Regards,
>
> Wiebe.
>
>
> "JimN" wrote in message

> news:506500000005000000AF6F0100-1079395200000@exchange.ni.com...
> > I've tried and it just asks, uninstall or repair. I have done both.
> > The last time I uninstalled and reinstalled but I still had to move
> > numerous files to the 7.0 folder. I'm think I moved all I could
> > locate. Something about it that even after I uninstall it still seeks
> > out the 6.1 folder to install into.
> > Jim
>
>
0 Kudos
Message 10 of 12
(3,503 Views)