Report generation toolkit: Avoid a separation of title and image at pagebreak in a work document.

I want to generate a report with the report generation toolkit in LV7.1.
In that report I use several report VIs to append text, titles and frontpanel images to a word document template (Office 2003). That works fine.
Depending on the size and text of my generated report, I have sometimes a problem with pagebreaks: A image is set to a new page if there is not enough space to place it on the old one. That’s ok. The text/title above the image is still on the old page. That's right, but I don’t want this. I know in Word you can use the paragraph formatting options to avoid a separation. But with the corresponding VI from the toolkit (word format paragraph (adv)) it seems not to work. With this VI you should have access to "indents and spacing" and to "line and page breaks". I always and only can change the "indents and spacing". En- or Disabling line or page breaks with this VI does not work, nothing changes in a word document.
Has anyone some suggestions or other solutions?
Thanks in advance!

Thanks for your input. You are right, that works and could be an alternative.
In the meantime I found a solution with creating my own activex vi instead of that from the toolkit as you can see in the attached image. Maybe this could help someone with similar problems...
Attachments:
KeepWithNext.JPG ‏46 KB

Similar Messages

Report Generation Toolkit Compatibility with Microsoft Office 2013 and LabVIEW 2012

Hello community,
on this page there is shown the Report Generation Toolkit Compatibility with Microsoft Office and LabVIEW.
In our company we use actually LabView 2012 and it works perfectly with MS Office 2010.
Has anyone ever tried the "Report Generation Toolkit" of LabVIEW 2012 with MS Office 2013? Does it really not work? Has anyone an emirical value for this topic?

Hi digital_badger,
as you sure have seen in the link it is not officially supported by NI, which means to you one of the following things:
1. You could upgrade your LabVIEW and your Report Gerneration Toolkit to Version 2014 and use MS Office 2013
2. You could just try it with MS Office 2013 which might work but if it's not working you don't get any support from NI.
Even if someone tried it already and it worked for him does not mean that it will work on your machines. It is possible that on some of your machines it could work but not on others. Their can be a lot of problems while playing around with unsupported setups.
3. You could leave your setup as it is and stick to your MS Office 2010.
I hope I could give you a good answer to your question

800706BA RPC server unavailable in Report Generation toolkit

Hi all,
I've got a problem with LabVIEW 7.1.1 and Report Generation Toolkit (RGTK).RGTK is used to connect to MS-Word, create a new document from template and report test results. Works like a charme when stying local on the respective test machine.
LabVIEWs 'Automation Open' node as wella as other parts of the RGTK have an control 'machine name' so I suspected I could bring a report server into game. Tried it and get an error "0x800706BA - The RPC server is unavailable in myTestVI" (translated from German Windows error).
All the required subVIs to create a document have been put into a small test app. This one runs fine when running on the desired report server, but fail when opened and run on the devellopment machine.
I have searched extensively for that error code and have changed some port settings in the firewalls and some services settings with no success. Can anyone help me out?
BTW, on the remote machine a new process named WINWORD is started, but nothing more.
TIA!

Hi Lul,
The error 0x800706BA is, as you said, a windows error (and, btw, your translation was correct as the original title is "The RPC server is unavailable").
You can try to fix it with MicrosoftFixit :
http://go.microsoft.com/?linkid=9666880
Beside, more links that could be of some use :
Windows Update error 800706BA:
http://windows.microsoft.com/en-US/windows7/Windows-Update-error-800706BA
Microsoft answer about error 800706BA:
http://answers.microsoft.com/en-us/windows/forum/windows_other-windows_update/microsoft-updates-fail...
In addition, a KB which is also related to this "RPC Server unavailable" in our IT database:
How to fix MSI software update registration corruption issues:
http://support.microsoft.com/kb/971187
Regards
Florian Abry
Application Engineer Group Leader
NI Germany

Problem building application using Report Generation Toolkit, LV 2011

I'm using LabVIEW 2011 under Windows 7.
I tried to use Application Builder to create an executable from a large body of code. One thing the application does is load VIs into a subpanel and run them.
Application Builder created the executable and gave no error message. The built application ran except that it couldn't run any of the dynamic VIs.
I finally succeeded in doing a screen grab on a transient dialog (about 1/10 sec. appearance). The dialog showed an attempt to load <vilib>:\Utility\NIReport.llb\NI_report.lvclass.
In one dynamic VI I commented out the call to the only VI that uses the Report Generation Toolkit (called only from dynamic VIs, all of which call it). Sure enough, when I built the application with that change and ran it, the dynamic VI that didn't invoke the Report Generation Toolkit did successfully load into the subpanel and run.
So, trying to prove to myself that that was the only problem, I wrote a VI that does nothing but load a VI into a subpanel and run it. User can choose one of two VIs: one that doesn't call the Report Generation Toolkit (or do much of anything), and one that does. Both VIs run fine standalone.
The not-much-of-anything VI loaded and ran in the subpanel. The other VI didn't--the same dialog, mentioned above, popped up for 1/10 second or less. Screen grab is attached.
When I included LVClass and NIReport.llb folders in the project (from vi.lib\Utility: Snapshot folders), and "Always Included" those folders (per a suggestion on this forum from a few years ago), the result was the same. The result was also the same when I included either one of those folders but not the other. Likewise it doesn't matter whether I add the dynamic VIs as "Always Included" or not.
Another piece of information that may be pertinent: when adding the NIReport.llb folder, I got a message that it was impossible to add a certain VI that's part of some report-type class, because a VI of that name already existed in the project. Screenshot of that dialog is also attached.
VIs and project file are also attached along with the two screenshots. I hardcoded VI paths, so put everything into C:\Testing if you want to see what the code does--or hack as desired, etc.
I will be deeply grateful for any help! And I apologize in advance if there's already some exact or close-enough solution posted--but I doubt there is. I looked around.
Thanks very much,
mws
Attachments:
Test-App-Build.zip ‏336 KB

Hi again,
If you extract all files in the original zip attachment to a folder called C:\Testing on a Windows 7 machine running LV 2011, and then use the build script within the project file to build the application, you can run the application and see what happens. You can also play around with the build parameters, rebuild, run, and see what happens then. You can also open my VIs and see what I'm doing.
The application lets you pick one of two dynamic VIs to run in a subpanel. One VI contains calls both to Report Generation VIs and some functions from the Advanced File Functions palette. The other VI does not.
When you pick the first VI to load and run (the one with the Report Generation and Advanced File Functions calls), it loads into the subpanel but is not executable.
When you pick the second VI to load and run, it does load into the subpanel and execute. So there's nothing wrong with the way I load and run a VI in the subpanel.
In the development environment, the whole thing runs with no problems.
Evidently the built application has problems resolving paths of something called by Report Generation VIs and by the Advanced File Functions I use.
I've done a lot of experimenting and no luck. I've looked in forum archives, etc. etc., for possible solutions. I'm hoping there's some simple solution I've missed.
Thanks very much for any help!

LabVIEW VI with Report Generation Toolkit elements in a TestStand sequence does not run with a LabVIEW 8.5 Run-Time Engine

Hi all,
I am using LabVIEW 8.5.1 and TestStand 4.1. I have done a TestStand sequence with a VI in it, which uses Report Generation Toolkit elements. On my machine I am using LabVIEW and TestStand with a Development System license. On the other machine I am using TestStand with a Base Deployment license and I have chosen the LabVIEW 8.5 Run-Time Engine in the Adapter Configuration. Everything is running well except of this VI with Report Generation Toolkit elements. The error message is showing that the VI is not executable. It works well only after I have installed LabVIEW with an Evaluation license and chosen LabVIEW 8.5 Development System in the Adapter Configuration.
I have found other posts and a document in the KnowledgeBase with a similar problem: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402?OpenDocument But I am not using EXE files in my sequence, so I don't know how to solve mine. Anybody has an idea?
Solved!
Go to Solution.

Hello guys,
thank you very much for your answers!
@Ruediger:
I tried to follow the instruction for Method 2 in the mentioned document: http://digital.ni.com/public.nsf/allkb/F3DC40A6E3F3B25B862570AD005D1D3D?OpenDocument, but the steps on my machine are different starting from step 4. After I click "Continue..." in step 3, I dont get a window, the system just makes a new folder with the same VI.
To be honest, I am new to LabVIEW and have some difficulties at this time. What I understood from your reply is, that I need to make a LLB-File, where the files from Report Generation Toolkit are in!?
@GovBob:
I was following the instruction in the document: http://digital.ni.com/public.nsf/allkb/9E00E7EFE0635E678625734600779EFE, but it wasnt working. Can you please tell me how I can check if the VI Server is installed and running on the machine?
I am using LabVIEW 8.5.1 and TestStand 4.1 on my machine, on the deploy machine there is TestStand 4.1.1. The version of my Report Generation Toolkit is 1.1.2.
Kind regards, Roman

MS Office Report (Report Generation toolkit) is not executable, Xnode broken?

Hi, I am trying to generate an excel report, and I figured it would be easier to use the MS Office report VI, but I am getting the broken arrow saying the SubVI is not executable and that the library that defines the xnode is broken... here is a screensot attached, I already uninstall and reinstall the report generation toolkit and still the same... this is what I found on NI: "This error occurs when the library that defines the XNode you used is broken. To correct this error, reconfigure the XNode." but no idea how to reconfigure xnode
Attachments:
Error.png ‏67 KB

What version of LabVIEW are you using?
What is the nature of your Report? What should it look like? What kind of data should it contain?
Can you show us some code that you've tried to use? If so, include the code as either a Snippet or as a VI attachment (so we can plug it into our own LabVIEW installations and experiment with it).
I generally find that the Report Generation Toolkit is a very easy way to generate Excel Workbooks. I work primarily with LabVIEW 2012 and LabVIEW 2014.
Bob Schor

Report Generation Toolkit Print HTML Problem

Hi,
i have a problem printing a html Page at a Costumers PC with the Report Generation Toolkit.
I use LV 2012 and the Report Generation Toolkit in 32Bit Mode.
The Target is a Win7 64Bit Machine with IE10 of our Customer with very strong security rules.
Our Programm generates a HTML Repor which is saved without any problem.
When i then try to print it with Print Report.vi it doesent work and i get error1 out of the SubVi NI_ReportGenerationCore.lvlibrint HTML Report using IE.vi.
This Sub.vi simply cant open the HTML Page with the IE.
I think its the costumers Security Rules that cause the Problem.
I saw a very strange behavior of the IE.
When i double click the .html file the IE gets opened and displays the file properly.
When i then hit the reload button it also gets reloaded.
When i click in the browsers adress bar and hit enter (Which normaly does a reload) i get an error "Adress Bar, Adresse, access denied".
And i think that happens in the Sub.vi.
I talked to some friends an they sad it could be that double clicking and reloding is done with the local user an the clicking and hitting enter reload is maybe the systemuser.
So i asume that the Sub.vi is also using the systemuser.
How can i determin which user is used to execute a vi?
Can i influence the user?
Has anybody a solution and seen this problem?
Regards,
westgate

If I understand your situation correctly, you are able to use the LabVIEW Report Generation Toolkit to create an HTML report, which you save as an HTML file. Can you open it in a browser and print it using the browser's Print button? I've use LabVIEW to generate HTML reports, but have never tried to print the Reports in LabVIEW -- I've always used the "browser route", myself.

Does the Report Generation Toolkit support Office 2007?

With the hot-out-of-the-oven Office 2007, Microsoft has done a complete overhaul of the Office environment that we all have spent many years learning to perfection (well.. almost). Lucky those who got a head start as part of the Office Beta program.
Well, NI claims that the current version of the LabVIEW Report Generation Toolkit supports "Microsoft Office 2000 (Word, Excel, and Graph) or later" and therefore literally also the new Office 2007.
I doubt that the ActiveX API has remained unchanged when developing Office 2007, so let's use this thread to uncover the experience you have with calling Office 2007 applications using the LabVIEW Report Generation Toolkit.
Anyone???
- Philip Courtois, Thinkbot Solutions

We are currently working on a maintenance release for the Report Generation Toolkit to support Office 2007. You can install the current toolkit with Office 2007, but you will have some problems. If you copy the four LLBs from the Compatibility\Office 2003\vi.lib\addons\_office folder on your Report Generation Toolkit CD to the corresponding vi.lib\addons\_office location in your LabVIEW folder after installing the toolkit, things will work for the most part. But you won't have 100% compatibility until the maintenance release is done.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Report generation toolkit (1.0) can't be installed under LabView 6.1.

When installing the toolkit, it showed that it was unable to locate the LabVIEW run-time engine of version 6.0 or compatible. However, my computer has already installed a run-time engine 6.1 (I saw it on my control panel->Add/remove programs). Do I need to install another run-time engine 6.0?

Hello William,
You may want to see this article on NI.com. It sounds like it addresses your particular issue.
Regards,
Chris J
Installation Errors with the Report Generation Toolkit 1.0 for Microsoft Office and LabVIEW 6.1
http://digital.ni.com/public.nsf/websearch/BEE4820C6BB7305186256B42005C9514?OpenDocument

Report generation toolkit how to access "title text" 1.1.3

Hi at all,
in LabView 8.5.1 with Report Generation Toolkit 1.1.2 I used the "Generate Report Get Modified Data.vi" and "Generate Report Set Modified Data.vi" to modify the Report Title Text. In the Version 1.1.3 of the toolkit I found no method to access this property.
Is there anybody solved this problem?
Regards,
Nicolas

Mike,
I'm creating HTML reports.
...and I found an unaesthetic solution (thanks to my college):
immediately after I created a new report, I'm searching in while loop for the first report with empty Title Text using HTML Data global.vi (or anything else in the cluster) and the previous HTML Ref-num is the according report. Now I can set the property using HTML Data global.vi again.
I won't suggest this if you're creating reports at more than one place, but in my case I can't get a race condition.
Nicolas

Setting the title font and axis labels in a graph created with the Report Generation Toolkit

I'm using the LabVIEW Report Generation Toolkit for Microsoft Office to generate Excel worksheets containing plots. Unfortunately, the default font size used in the plots is huge (see attached worksheet). I was able to use Excel Set Graph Font.vi to reduce the size of the axis labels, but there does not appear to be a function to do this to the title and legend. In addition, there does not appear to be a function to set the axis text labels. Before I write my own, has NI released additional functions to perform these tasks?
Thanks for your help,
Zach Lerner
Software Engineer
OnWafer Technologies, Inc.
Attachments:
Test1_-_embedded_graph's_title_and_legend_font_is_huge.xls ‏14 KB

Hello Zeidan
The graph title and legend font sizes can be changed by accessing a low level VI (Excel_Insert_Chart.vi) that is part of the excelsub.llb that is located at (C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\addons\_office). This VI is called dynamically from within the Excel Insert Graph.vi and it uses VI server technology to access the Excel exposed properties. Attached to this post is an image of the block diagram of this VI after I have modified it to set the font sizes of the title and legend to 15. The circles in the image represent what I had to add to accomplish this.
Best Regards,
Ayman Kabire
Attachments:
Excel_Insert_Chart.JPG ‏99 KB

Report Generation Toolkit V9.0.0 : Print Report.vi doesnt print

Hi,
i have migrated my Labview 8.5 Project with Report Generation Toolkit V1.1.2 to a Labview 2009 System with Report Generation Toolkit V9.0.0.
In this Project I use the Report Generation Toolkit for printing out a Standard Report with e few Tables and Graphs.
Now the VI Print Report.vi delivers the Error -41002 with the Text "Invalide Printer Name". I have, of course installed the propper Printer on the machine.
I don´t connect a string to the "Printer name" input of the VI, because i want to use the default printer.
In my oppinion, there´s a bug in the Print Report.vi: if you don´t wire the "Printer name" input, the vi should use the default printer, but in this case the vi connects the empty input string to the input of the method node it calls.
I fixed this bug, but the method node still returns the same error.
any ideas?
Thanks!
Solved!
Go to Solution.

Thank you for the link!
For some reasons i can´t find this specific article in the knowledge base (my browser is always rerouted to the german version of ni.com, because i am in Austria). I tried to search with the exact title of this article, and the error message string, but no results...
I have also installed Labview 8.5 and the "old" Toolkits on my new computer in addition to Labview 2009 and the "new" Toolkits and tested my program in 8.5. Here i got an error mentioning the margins and i had to change the margin settings for printing out, then in worked.
After reading the article, i have applied the same changes for the margins in the 2009-version of my program and it works too!
Problem solved!
Thank you very much!
PS:
I first wrote, that there´s maybe a bug in the new version of the Print Report.vi, but i´ve compared it with the old version and it seems to be no bug, sorry!
After all I decided to stay with Labview 8.5 for now, because of another problem:
it´s not possible to "save for previous version" from LV2009 to LV8.5 directly.
Laview crashes, when a VI contains an event structure as i found out by searching through the "known issues", and i have a lot of VIs with event structures!
I have to have the possibility to save my Labview projects for 8.0 and 8.5. The only way is to save for 8.6 and then save from 8.6 to 8.5.
That´s nasty and time-consuming!
Maybe a future update will solve this problem (without producing new ones)

Report Generation Toolkit - Prints data from a previous report in Word

I am running an executable from the "system exec.vi" created with Labview 6.1. I am using the Report Generation toolkit vi's to create a report in Word that prints simple Title with test header and then appends a Table with measurement data. The problem is the measurement data in the table is from a previously printed report. This problem only exists when I Run the Report.exe from the "System Exec.vi". If I manually start the Report.exe in Windows or open in the Windows Commandline the correct data measurement data is printed in the report table. Any suggestions are appreciated. Thank You

Hi,
So far I havent been able to reproduce this on my computer. Could you post your code so that I can try and reproduce this issue?
Feroz P
National Instruments

Can't print to Epson TM-U590 Slip Printer from Report Generation Toolkit with LabVIEW 8.6.1

Hi all,
I have an application that uses the Report Generation Toolkit to print tickets to a docket printer. Usually this works fine - I have 8 existing installations where there are no problems
I'm currently installing the software at a new site that uses an Epson TM-U590 slip printer and I can't for the life of me get printing to work
Using a Standard Report, the Print Report.vi returns error -41002 which indicates it can't find the printer. I've opened up the VI using remote debugging and it does find the printer name correctly with the Query Available Printers.vi. It gets an error code -2147352567 from the Printout node, which then gets replaced with the -41002 error which is reported.
For historical reasons I'm still using LabVIEW 8.6.1 for this project. I'm considering moving to 2011 or 2012 but I've had reliability issues with other parts of the application after attempting to update to a newer LabVIEW version so I'd like to avoid that at this stage.
The application is running on a standard desktop PC with Windows 7. The slip printer works fine if I print to it from Notepad, and my application is happy to print to any other printer, just not the slip printer.
The slip printer is using the LPT port. Previously the docket printers I've used have been USB but I would expect the printer driver to hide this detail from the application...
Any ideas would be much appreciated
Cheers
Brett
Senior Software Development Engineer
Certified LabVIEW Architect and LabVIEW Champion
Solved!
Go to Solution.

I've managed to sort out the problem, thanks to this KB article: http://digital.ni.com/public.nsf/allkb/67D60209102E2161862568AC0074BF64
I'm now having the same issue with a Star docket printer (a TUP592), this time with another program developed in LabVIEW 2011.
As mentioned in the article, the problem is actually to do with the margin settings rather than the printer name, despite what the error message says
After some experimentation, I've gotten the Star printer to work by setting a large (>14cm) right margin. No idea why this is required as it seems to print right up to the right edge of the paper quite happily, but there you go.
So I haven't defintely fixed the original problem yet as I haven't gotten back to the site, but hopefully this will be of some help to someone else.
Cheers
Brett
Senior Software Development Engineer
Certified LabVIEW Architect and LabVIEW Champion

Report Generation Toolkit and App Builder question..

Hello,
I am in process of modifying my test code for writing my data to Excel. When I first developed the tests I did not have the Report Toolkit of Excel so I built the ActiveX VIs I needed. Now since I have upgraded to 7.1.1 with the MSOffice Toolkit I am rewriting my test code to use the toolkit VIs as it seems to work much better and faster then what I had done.
My question is this. Since I have my testcode distributed to multiple machines when I build my App, do I need to add every Dynamic VI within the toolkit to my App? if so is there and simple way to find exactly which dynamically called VIs are used within the toolkit VIs?
Thanks
Jeff
Jeff D.
OS: Win 7 Ultimate
LabVIEW Version: 2011,2010,2009 installed
Certified LabVIEW Architect

Greetings jdebuhr ,
I'm using LabView 7 and have the report generation toolkit, In the "Report Generation Toolkit User Guide.pdf" manual under the title Cearating stand alone applications you 'll find the names and the path of the required dynamic VIs to be included in your EXE file (using appliocation builder)
Check this manual.
Ayman Mohammad Metwally
Automation Engineer
Egypt - Cairo

Report generation toolkit: Avoid a separation of title and image at pagebreak in a work document.

Similar Messages

Maybe you are looking for