Built applications not printing

[Novatronics]

Hey all,

I am experiencing some problems with what appears to be the application builder.  I have a number of programs written, which perform tests - the results from which are compiled into a report and printed.  Everything works fine during development, and I can run the whole program perfectly and print properly.  The problem lies in when I build program into an application.  I can achieve all the same functionality as during development, except printing.  When I click "print" (control on my front panel), nothing happens.  No errors or anything, just nothing.

I have read that some people had problems with file paths in built applications, but that's not a problem with me, since I can create an entirely new report (no references to outside files or anything - all LabVIEW created), and the same problem occurs.

Has anyone else had this happen?  Anyone have any ideas?

Thanks

[bob_miller]

This may be a long shot, but does the print operation involve communication through a
firewall? I had a similar mystifying problem which I tracked down to an issue where the
firewall allowed "LabVIEW 7.1" to do whatever it wanted, but not "MyApp.exe". So my
development VI worked great, but not the deployed application. Once I configured
the firewall to allow the right network access by the application, all was well.

Rerunning the application with the firewall temporarily disabled is one quick way of
checking this.

Bob

[Novatronics]

Thanks for the reply Bob.  Unfortunately though, this isn't the problem.  My network has a firewall to the outside, but none of the individual computers in the network are firewalled.  Still haven't figured out what it could be though...

[Dennis_Knutson]

Are you using the built-in report generation or is the add-on? If it's the built-in, does it work on the development machine but not when you deploy it. If it doesn't work on a pc other than the development pc, you need to create an installer and make sure NI Report Support is selected from the Installer>Advanced dialog. I don't have the NI report gen toolkit but I know that there are additional support files that need to be installed with that as well.

[Novatronics]

Thanks for the reply Dennis.

I am using the built in version of app-builder, and I am experiencing the problem on the same machine on which both development and deployment occur.  I have actually tried this on two different computers which were used for both develoment and deployment, with the same results.

I have since email NI support in hopes of an answer...

Thanks for everyone's help.

[Marc_A]

I had this happen to me.  The problem I was having was that I was printing from a VI that I loaded into a subpanel, and when I built the application, I didn't include it as a dynamic VI.  Therefore, the report generation VIs weren't getting included.  It's probably a long shot, but I figured I would just let you know what solved it for me.

[devchander]

Hi,

Include suitabel add on files as Dynamic VI's on the source Files tab of build EXE.

Its default path is C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons\_office. here choose teh suitabel add on VI for word or excel report generation

Hope this helps

Regards

Dev

[Gurdas]

Hi,

We faced a very similar problem and solved it by adding the Dynamic VIs for Word and Excel when building the EXE (or Installer).

If I understand you correctly, you are using the report generation toolkit and when you click on the "print" button, you expect the code to build a report document (in maybe word or excel) and which then you would like to print the way we print any word/excel file. What you might be seeing is that on clicking "print" in your application there is some harddisk activity but nothing comes up on the screen; i.e. the report does not get generated.

The answer lies in the readme.rtf file that comes with the report generation toolkit. I have attached a copy of the same. I have also attached another file put into pictures what is already written in the readme.

Precaution: The target PC should have the same version of MS-Office as the development PC. We have so far found no problems even when we break this rule for Office 2000 and Office XP. But I do know of problems arising if one of them is Office 97.

Hope this helps.

- Gurdas