Report Generation in Executables

[Jason-H]

Does the target machine have the file to which you are trying to write? If that file doesn't exist, the application will open an empty word document.

[RandelPrandel]

HI Jason, 

I don't understand what that means. 

It does not look for a file to write in. There's no name to the file, it creates a new file everytime which has to be saved later. 

Thanks, 

RP.

[Jason-H]

I wrote a simple program that writes a string to a word document. All I included was the NI_Word.lvclass and the executable ran fine. Can you explain to a little more what is happening? Error codes?

[RandelPrandel]

Hey Jason,

I fixed the error on it. The error was from a path for a JPEG hardcoded into the vi which wasn't being transferred to the executable. 

I built a path for the executable via application directory and it worked.

* The reason it was spitting out a blank word document is because the very first field in the word document is the JPEG, so it would essentially stop executing at the JPEG and would not proceed further. 

   I found this by enabling the debugging option on the JPEG.  

The error code was 2146823136. 

RP. 

[HermanYang]

I have same problem  -- can't open the excel file with executable file but can open with vi file.

I try to understand your answer but still not be able to add what you mentioned in "Always Included" in the Source File Settings.  I get to Excel folder under NI_Excel.lvclass, and don't know what to select and don't know what should I do.  Would you please explain in more detail how do I add the required lib file? Thank you so much.

[Bob_Schor]

What version of LabVIEW are you running?  I've built executables in LabVIEW 2014 that use the RGT and the only file listed on the Source page was the Top Level VI.  There were no "Always Included" entries, and the RGT loaded fine.  I haven't checked recently, but I'm 95% certain that the exact same code with the exact same build also worked in LabVIEW 2012.

[HermanYang]

I use 2012 version.

The error says the problem on path

 Final Functional Test.exe\labvi3w\vi.lib\Utility\NIReport:llb\Excel\NI_Excel.lvclass

I am not sure how do I add NIReport:llb ( if this is the one I missed in my build) for executable file.

[Bob_Schor]

Older versions of LabVIEW needed to have pieces of the RGT in the Always Include section of the Build Spec, but I don't think you should need this in LabVIEW 2012.  Do a Web Search on Report Generation Toolkit in Executables and you should find the older "How To" instructions.

If they don't fix it (and I'd gues they won't), then you'll need someone to take a look at your entire Project.  If you're not comfortable attaching a ZIP file of your entire Project, you have two choices (besides "do nothing") -- try to create a small "Demo" version that has just enough code to illustrate the problem (start by copying your Project to a different folder, rename the Project in the new folder, then start "discarding" code that is irrelevant to the RGT problem) and post a ZIP of that Project for us to inspect, or send a Private Message to a Forum Member of your choice offering to send your entire Project to him/her if he/she agrees to try to help you.

Bob Schor 

[HermanYang]

I finally figure it out, what I need is to add NI_Excel.lvclass in the source file. Thank you for help.