LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

MS Word report not visible in executable

We are using LV 7.1 FDS (with app builder) on Win2000 prof. We have Report Generation Toolkit and Database Connectivity Toolkit installed (among others). Our VI publishes reports in MS Word. When the user clicks the "report" button, the VI generates the report and this is available to the user on screen. No file is saved and the user has the choice to save the report with any name.
The report function works fine in VI state.

But, when we make an EXE of the VI the behaviour of reporting changes. Now, pressing the "report" button triggers harddisk activity but nothing comes-up on the screen. There is no report to be seen on either the screen or the taskbar!! In the VI, the taskbar shows a word document and the report is accessible when the user clicks on this.
The amount of disk activity is similar to the case when we were generating reports in our VI.
The EXE is being tested on the same machine as the VI.

We have tested on 3 machines (with Office 200 and Office XP) but the problem remains.

What could be going wrong?

An early answer would be appreciated.

Thanks,
Gurdas
Gurdas Sandhu, Ph.D.
ORISE Research Fellow at US EPA
0 Kudos
Message 1 of 5
(2,659 Views)
Have you tried to make Word visible with the property node?
0 Kudos
Message 2 of 5
(2,650 Views)
Hi Gurdas,

If you use report generation toolkit's VI to build executable program, you need to add dynamic vi for the toolkit when building application. In Build Application window, click Add Dynamic VI... and go to C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons\_office\_wordsub.llb then choose _Word Dynamic VIs. Please try to build it again and reply if there are any problems.

Bill
Message 3 of 5
(2,636 Views)
Right on, Bill! There's a KnowledgeBase discussing this same operation for Excel that you can refer to: KB 3DCF4P4P: Executable using New Report.vi Does Not Open Excel Automatically

Good luck!
0 Kudos
Message 4 of 5
(2,610 Views)
Bill and Kileen,

Thanks both. That is just what was needed. I tested and it works fine now.
The same is also mentioned in the User Guide / Release Notes that accompanied the toolkit.

I happened to collect some other webpages and .pdf that talk of other issues. In case someone happens to need this (.zip file would be less than 1 MB), please feel free to write at gurdas@qagetech.com

Best regards,
Gurdas
Gurdas Sandhu, Ph.D.
ORISE Research Fellow at US EPA
0 Kudos
Message 5 of 5
(2,596 Views)