12-11-2009 08:00 AM
Hi,
I am building an exe of a program that use some simple VIs to generate an HTML report (so I didn't need Report Generation Toolkit);
in the build I found a lot of VIs included in 3 directories: NI_HTML, NI_Reports, NI_StandardReport....are all of them necessary??
Is there any way to avoid this? Shoudn't the RunTime engine include them?
I am using Labview 2009
thanks
Solved! Go to Solution.
12-14-2009
02:27 AM
- last edited on
06-26-2026
08:43 PM
by
Content Cleaner
You did use Report Generation Toolkit!
See here [broken link removed; article no longer available]
12-14-2009
04:26 AM
- last edited on
06-26-2026
08:44 PM
by
Content Cleaner
Hi antea06
the newreport VI that you use to build your HTML report uses class object as you can see on the screenshot below. There isn't any way to avoid this situation; the runtime engine include them by default.
I suggest you to see this document [broken link remove].
Ciao!
12-14-2009
04:57 AM
- last edited on
06-26-2026
08:45 PM
by
Content Cleaner
Sorry antea06,
this is the correct document [broken link removed; article no longer available].
12-14-2009 06:04 AM
Hi, thank you for the INFO.
I supposed there was no way to avoid this.
I don't like to deliver such a build to the client so I build an HTML without Report Generation VIs.
Bye
07-23-2010 12:55 PM
Although I've used the Report Generation Toolkit for some projects, I have avoided using it for those deployed as executables ever since the LVOOP transition caused the distribution to blow up. I'm looking for an html solution again for an executable. Is anyone aware of a third-party html LV tool that can create simple reports and doesn't require the Report Generation LVOOP bloat in a distribution?
Thanks,
DaveT