LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??
Message 1 of 10
(4,777 Views)
Hi,

This error is caused because the application is not able to find the path for the _exclsub.llb and excel.llb. If you look at the New Report.vi there will be a subvi that returns the application path. This path generally points to /.

For eg.
If you are creating an application called Dothis.exe (in c:\dothisfolder) using labview and while creating your application you saved the support files in c:\dothisfolder\data, then the application would look for the _exclsub.llb in the latter folder. So make sure that you have these 2 llb's there.
0 Kudos
Message 2 of 10
(4,776 Views)
I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.

Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?

I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.

I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?



Any ideas ?

Greg Klocek
0 Kudos
Message 3 of 10
(4,776 Views)
Actually the "New Report.vi" does not generate the Error "ERROR 7 occurred at OPEN VI Reference in NEW REPORT.VI->PrintLabels->Main.vi" but it is every call to every Report Vi like, SetMargins, PaperSize, AddField, CloseReport, etc. I repeat the "New Report.vi" does not itself generate any errors.

Greg
0 Kudos
Message 4 of 10
(4,776 Views)
You have to include as "Dinamic vi" in Source file the vi: _Word Dynamic VIs.vi. in the following library
...\National Instruments\LabVIEW 6.1\vi.lib\addons\_office\_wordsub.llb
Message 5 of 10
(4,776 Views)
Adding the "_Word Dynamic.vi" as a Dynamic VI in the Build Script solved the problem. THANKS! I really, really wish Labview would list the FILENAME of the File that is Missing for ERROR #7. If a File is missing then Display the Filename so at least I chance to fix the problem. "Error #7, File Missing" is so vague.
Greg
0 Kudos
Message 6 of 10
(4,777 Views)
This is interesting because I've never had to do this in the past - just adding _wordsub.llb as a support file worked fine. I was issued a new computer and installed the same LabVIEW 6.1 and Report Gen. 1.0.1 software, but I was getting Error 7's until I added _Word Dynamic VIs.vi as a dynamically called vi.

What changed?
0 Kudos
Message 7 of 10
(4,776 Views)
Just had the same issue today with LV 8.0.1.  Driving me crazy!!!!
Matthew Fitzsimons

Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
0 Kudos
Message 8 of 10
(4,442 Views)

Are you using the Report Generation Toolkit 1.1 or later?  If so, all you need to do is add vi.lib\addons\_office\_exclsub.llb\_Excel Dynamic VIs.vi and vi.lib\addons\_office\wordsub.llb\_Word Dynamic VIs.vi as dynamic VIs to your application.  Once you build, it should be fine.  The approach described above, where you add the LLBs as support files, no longer works with the Application Builder in LabVIEW 8.0 or later.

-D

0 Kudos
Message 9 of 10
(4,437 Views)

Thanks!  A frustrating error beause it thinks it is is a dynamic VI but it is in line code.  I have it working now thanks to this thread. 

Have a good New Year.

Matthew Fitzsimons

Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
0 Kudos
Message 10 of 10
(4,426 Views)