08-24-2006 05:47 PM
08-25-2006 01:13 PM
08-25-2006 02:00 PM
Hi Mike,
I actually found a work around yesterday and it looks like the installer has been working ever since. I noticed that the lvjpeg folder appears in the installer source files when I add _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi to the project from their original location in the _exclsub.llb and _wordsub.llb files located in C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\addons\_office. If I do a save as and save the VIs into the folder where my project.lvp file is, then the folder does not appear in the installer source files and everything builds fine. I still do not understand exactly why this is so.
Could you help to explain?
Thanks,
Brandon
08-28-2006 05:11 PM
08-28-2006 06:20 PM
Hi Mike,
I think that's exactly what happened. When I updated to LabVIEW 8.20, I uninstalled everything then did a reinstall. This was because when I tried to open my project that I started in version 8.0.1, there were so many files (VIs) missing and I couldn't find alot of them.
08-29-2006 01:40 PM
08-29-2006 06:34 PM
10-12-2006 02:34 PM
I had the same problem with the lvjpeg folder as Brandon. I had just built another application where the problem did not occur, but my new project used the Report Generation Toolset. So I included the _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi in the project. When I built the executable, the lvjpeg folder was displayed as a part of the executable package. Then I built the installation package, I got the same error message. And as it turns out, I had also completely deleted all NI products from my workstation so that I would have a clean install of LV 7.1, LV 8.0.1, and LV 8.2.0. (Of course, the Report Generation Toolset only works on the LV 8.2.0 installation, sad to say).
Any way, rather than just copying the files to my project heirarchy, I opened the two VIs (_Excel Dynamic VIs.vi and _Word Dynamic VIs.) and noticed that they had the unsaved asterisk (*) in the title bar. I "Saved All" and that fixed the problem.
Chuck
12-10-2006 09:24 AM
Chuck,
Thanks for your suggestion. I recently had the same problem and your suggestion about opening the dynamic VI files and saving did the trick.
01-22-2007 07:07 PM
Chuck,
Worked for me too, Thanks.