Report generation toolkit help

Hi,
I have created a simple example to demonstrate my needs.
Is it possible to write 16 numeric values (from my 16x for
loop) “press and temp”, to my new report (from my defined template).
My two main issues are:
Each time it iterates through the loop, it floods the
defined ranges with the same press and temp values. As I have defined my range
as being 16 deep, i would like each iteration of the loop to incrementally populate
the next available cell only.
Considering the above i would also only like one excel book
to be opened then populated incrementally. What is happening just now is, for
each iteration of the loop it creates a new book. Which, to be honest is what I
expected to happen, but not the behaviour im looking for.
Any ideas?
Many thanks
Solved!
Go to Solution.
Attachments:
Untitled 1.vi ‏9 KB
d.vi ‏54 KB
Book1.xltx ‏9 KB

ok,I worked away at this a found the solution to my own problem, pitty i cant give my self some kudos love :-)
anyway, i have attached my solution in case anyone else finds this useful
Cheers
Attachments:
Write Data.vi ‏24 KB

Similar Messages

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

Hi Leo22,
Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

Need help with report generation toolkit

I'm having a really hard time finding a solution for my problem. I'm measuring a distance and a diameter simultaneously. The outcoming values have a depency and are stored in a 2-D array. I want to export this array to an excel table and x-y-chart (distance is x and diameter y). So far I can export the data to a table, however the charts produced are useless. Can somebody please help me? I'm almost crying since I'm trying to find a solution for 3 days now.
Additionally, after one measurement is done, the user should have the possibility to do the next measurement, and the data has to be stored in the same excel file, in another worksheet. How can I do this?
Attachments:
Hauptprogramm_0.5.vi ‏129 KB

Hi!
If you want a nice graph in Excel based on your data you have input there, I would recommend creating a macro that builds your graph. Read more about macro, Excel and LabVIEW here. I don't have the Report Generation toolkit, but I think you can send macros with it too.
Regards,
Even
Certified LabVIEW Associate Developer
Automated Test Developer
Topro AS
Norway

Report generation toolkit and signal express user step : problem of closing reference in "Stop" event

Hi all,
I'm trying to make a package of Vis to easily make Excel reports with Signal Express. I'm working on LabVIEW 8.2.1.
I'm using the report generation toolkit, so I build a .llb from my project which contains all the hierarchy of my steps, but also the hierarchy of dynamic VIs called.
I have made some steps, like "Open Workbook", "Write Data", etc.
My steps run well, excepts one step : "Close Workbook".
If my "Close Workbook" step is firing on "Run" Signal Express event, I have no error, so my reference is properly closed.
But if my "Close Workbook" step is firing on "Stop" Signal Express event, I have an error "1", from "Generate Report Objectrepository.vi".
I feel that I'm trying to use a reference which has been killed in the "Stop" step...
I would like to know what exactly do Signal Express on "Stop" event and why my close function does'nt run well.
Thanks,
Callahan

Hi Callahan,
SignalExpress (SE for short) does the following on the Stop event:
1. Takes the list of parameters that SE found on your VI's connector pane, and sets the values that the user set from the "Run LabVIEW VI" configuration page, if any.
2. Then tells the VI that SE is running the Stop event by setting the Enum found on your VI's front panel. This in turn should produce some boolean values telling your VI to execute the Stop case.
3. The VI is then run, with those values and states.
4. SE checks to see if any errors where returned.
5. Since this is the Stop event, SE releases the reference to the VI which it possesses.
Questions for you would be, is the reference to your Workbook linked to a control on your connector pane, or held in a uninitialized Shift Register. If it's held in a Shift Register, SE would not be aware of it, and would not be able to affect that reference.
Hope that helps. Feel free to post your LLB if it doesn't.
Phil

Report Generation Toolkit Error

I have an application that generates multiple excel spreadsheets each containing a table and four graphs. This has been working fine for three months but I am now getting error when generating the reports. The source of the error is in the Excel_create_workbook as indicated on the attached picture. I am passing in a template name for my excel reports. The error code (-2147352571) states a type mismatch. The file path to my template is a constant so I can't see how sometimes I get a type mismatch and other times I don't.
Any help on this would be greatly appreciated.
Thank you,
AJL
Attachments:
create_Workbook error.JPG ‏269 KB

Thanks for the reply, however, this VI is part of the Report Generation Toolkit so I don't want to have to modified NI's code if possible. I did try your suggestion without saving the VI and I still got the same error.
Any other ideas?
BTW - I encountered this problem first in an executable but have since seen the error in the development code.
Does anyone know if there is a limit to how many times you can create an excel document from LabVIEW? I wouldn't think so but the error seems to happen if I try to create several (more then five usually) documents at a time.
Thanks in advance
AJL

Report Generation Toolkit Installation

Hello!
I need to install the Report Generation Toolkit, but only using Excel 2007.
Is this possible? Or will we need to install a full Office suite? Is there a way to workaround full install?
We'll only be using Excel anyway...
Thanks!

Hey Oley,
I have been doing a bit of research and what I found is that there was a corruption in the Windows Installer database. You can use the "Windows Installer Clean Up Utility" downloaded from Microsoft to remove ALL traces of Office, and then reinstall. This should solve the problem. I found this in another discussion forum with someone else with a very similar issue. I hope this helps!
Carla
National Instruments
Applications Engineer

Report generation toolkit conditional format - how to?

Hi
We are using the Report generation toolkit (2010 version), and have a question regarding this tool.
I see functions for setting the number format, but not a conditional format. Does this not exist?
http://zone.ni.com/reference/en-XX/help/372120A-01/lvoffice/excel_set_cell_format/
This page refers to an example which from the name sets a conditional format. However as I understand it, this example is setting a custom number, not a conditional format.

Hi,
the simplest way to do this I guess you can provide a template for your Excel sheet, where you can set the conditional format there.
From LabVIEW you can just send the values into this sheet-template.
Maybe you can try these if you want
http://forums.ni.com/t5/LabVIEW/Using-conditional-formatting-in-excel-through-LabVIEW-activeX/td-p/1...
http://forums.ni.com/t5/LabVIEW/Excel-Colour-properties-modified-via-LabVIEW/m-p/573748?query.id=218...
Regards,
Yan.

Error -2417417851 using Report generation toolkit

I try to use the Report Generation toolkit (Version 1.0.1) for MS Office und the example "Generate Report from Template (Excel).vi" return an Error -2417417851
I run Labview 6.02, on Win2000 German, and use Office 97 (Everything is installed (included MS Graph))
Did someone experienced such a problem and found a solution?
Thank you for your Help!

Is LabVIEW and Office both German? Under Control Panel >> Regional Options >> General, is the language set to German? How about under Regional Options >> Input Locale? Reboot if you make any changes.
I would suggest reregistering the nireports.dll. It is located in the National Instruments\Shared\NI Reports directory.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/4f811a9b23f1d46e862566f700615b7a?OpenDocument
Next, mass compile (Tools >> Advanced >> Mass Compile...) the LLB's in the \vi.lib\addons\_office
Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

Report Generation Toolkit 1.01 and broken arrow

Hi,
I desperately need help because I need to build my application tomorrow morning for our production department and have trouble with the report toolkit.
I am aware of your knowledge base entry regarding this problem. I already deinstalled and reinstalled the toolkit (version 1.0.1 for LV 6), and I checked the windows registry entries. Still, after mass-compile, the report generation toolkit VIs are not executable (broken arrow, invalid property node). I have LabVIEW 6.02, 7.0 and 7.1 on my computer and I am using the report generation toolkit version 1.0.1 with LabVIEW 6.02 and version 1.1 with LabVIEW 7.1. The application that I need to build is written in LabVIEW 6.02. What else can I do to get rid of the broken arro
ws?
Thanks in advance for your fast answer....
Gabs

Hi,
the problem is the following: during the build error 1003 occures at ....\internal.llb\Word_New_Page.vi. Possible Reasons: LabVIEW: The VI is not executable. When I open my main VI, I see no broken arrow. When I force a mass-compile (Strg+Shift+Run button), the broken arrow appears suddenly. I can then see the following error message: Word Easy Text.vi is broken because Word Format Text.vi is broken because the Property Node Range\Style calls an invalid property. Actually, the property nodes in these VIs have NO properties and the invoke nodes NO methods.
I know now that this is due to the fact that I need to build this application for a computer on which Word97 is running, so I installed the Report Generation Toolkit for Word97. But - on my developme
nt computer where LabVIEW is installed Office XP is running, not Office97. If I install the Report Generation Toolkit for OfficeXP, no error occurs during the build, but the executable does not run properly on the target computer (when calling Word97).
Question for NI: How am I supposed to build an executable using Microsoft Word Report Generation Functions if the target computer has Word97 installed but the development computer has WordXP installed???
Please help,
thanks,
Gabs

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!

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

Word report generation toolkit error with Win 7 LabVIEW 2013, Word2010

Hi All
I'm seeing different Errors using the Report generation toolkit. Maybe you can help me with that.
The errors are:
-2147417846, application is busy in Word_Get_range.vi
-2146824090 Exception in Microsoft word: Befehl misslungenHelp Path is wdmain11.chm and context ...
-2147417846 application is busy in Word_Quit.
the error messages are attached to the post.
I'm testing 10 sensors with one application and want to run up to 5 applications on one computer. Since I'm seeing such errors as application is to busy I set all my report generation vi's as non-reentrant execution and additionally added some pause after each word modification.
But I'm still seeing such errors when I run two applications on one computer.
What is the best way to deal with these errors?
thanks
best regards
Urs
Attachments:
exceptionerror.PNG ‏20 KB
BusyActiveX2.PNG ‏20 KB
BusyActiveX.PNG ‏22 KB

Here my Vi's involved in creating the report.
Is there a way to check wheter word is busy or already open?
Attachments:
save report as PDF.vi ‏26 KB
create_report.vi ‏70 KB
Word_Update_Table.vi ‏34 KB

Error 7 with Report Generation Toolkit

Hello Everyone,
I'm trying to generate an Excel sheet report for some readings using "Report Generation toolkit" But when trying to generate the report, the report generation part of code is executed and gives Error(7) and there is no report is generated.
The Code I use is atached in the following Link:
https://www.dropbox.com/s/9n4brimucsd0xts/Report%20Generation.rar
Can I get help please?
Thanks in advance
Solved!
Go to Solution.

I was able to download and open your compressed file. I unpacked it into a folder.
There are numerous peculiarities that lead me to ask "Are you trying to learn LabVIEW on your own, without a mentor and without training and guidance"? Here are some of the things that I noticed:
Although a Report Generation .lvproj, .aliases, and .lvlps file, the Project, when opened, was empty! Since Projects were added to LabVIEW, almost all development should take place in a Project, but you do not appear to be doing so.
You have an Event Loop (good) to handle pressing Start, Stop, and Report buttons. But instead of using Boolean controls with a Latch property and using a "Value Changed" event, you use Switch Until Released (which, so far, I've never used) and a Mouse Down Event. I suppose this could work, but I've never seen this pattern.
You are writing an Excel Report, but are not using the Excel-specific VIs (such as Excel Easy Table). Why (or Why Not)? The basic idea of an Excel Report is that you create the 2D text data you want to write into Excel, then with a few simple VIs, you open Excel, write the Table, and save the Report. In particular, you don't write out something that resembles the columns of the first few rows of a Spreadsheet (Date, Time, Test, etc.).
Now to your specific question, Error 7. Do you know what this error means? If you click on Help, choose Explain Error, and put in 7, you will see this means "File Not Found". Well, there is an obvious place where a File is used, right when your program starts. I recommend that you put a Probe (do you know about Probes?) or an Indicator on the path going into the main For loop and see what File you are trying to open (hint -- there's an error in the way you build the path, but you should be able to figure out how to fix it).
Good luck. Hope these suggestions get you on a Better Path.

Error 10 when building an application in LV8 and Report generation toolkit 1.1.1

I am trying to build an application using LV8.0.1 and Report generation toolkit 1.1.1 and i get this error.
Error 10 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
Any ideas?
Scientia est potentia!

Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Running macro on Table using Report Generation Toolkit and Office 2003 Incompatible!!!!!!!

Hi,
I am using some functions under the Report Generation toolkit (LabView 7.1). We recently updated our test PCs from Office 2000 to 2003. The "WORD IMPORT MODULE.VI" returns error code -41113 when used with Word 2003. No problem on Word 2000.
In fact even the example VI available under Find Examples - Run Macro on Word Table fails and returns error code -41113 when "WORD IMPORT MODULE.VI" is called on Word 2003. Word 2000 is OK.
Any one faced this problem???? Any solution to this problem??
I would greatly appreciate your feedback / suggestions.
Thanks,
Mim

darren,
thanks for your reply.
After checking the the property "Trust access to Visual Basic Project" , I get the following error message:
Exception occured in Microsoft Word, Unable to run the specified macro. Help Path is C:\Program Files\Microsoft Office\OFFICE11\1033\wdmain11.chm and context 37401 in Word Run Macro.vi->SetFirstRowAsTableHeaderforWord(Macro).vi->Generate Report.vi
I can run the macro directly from Word.. no problem running macros in Excel dirently either. I get error message only when running macro from LabView. So, I doubt if it is an IT issue.
You don't have a problem with Word 2003 and Word Import Module.vi???
I am attaching my Vi-Report Generation.vi and the subvi. I would so much appreciate if you run ReportGenerate.vi on your PC and let me know if there is a problem.
Many Thanks for your help.
Mim
Attachments:
ReportGeneration.zip ‏75 KB

Report generation toolkit help

Similar Messages

Maybe you are looking for