Report Generation libraries

Hi Everyone
I have a problem with the report generation tooolkit. I found the error and it was reported to NI. Here is the link:
http://digital.ni.com/public.nsf/allkb/1A12BE048F6D7B15862577A00064C4D0
It says:
Installation Instructions
Close LabVIEW
Replace the following files with their attached counterparts
..\National Instruments\LabVIEW 2010\vi.lib\Utility\NIReport.llb\Word\NI_Word.lvclass
..\National Instruments\LabVIEW 2010\menus\Categories\Programming\NI_ReportGenToolkit_Menus.lvlib
..\National Instruments\LabVIEW 2010\vi.lib\addons\_office\NI_ReportGenerationToolkit.lvlib
..\National Instruments\LabVIEW 2010\vi.lib\Utility\NIReport.llb\Excel\NI_Excel.lvclass
Mass compile the following directories
..\National Instruments\LabVIEW 2010\vi.lib\Utility\NIReport.llb\
..\National Instruments\LabVIEW 2010\vi.lib\addons\_office\
I do not understand what does it mean when it says to replace the files. At the bottom of the link it has a zip file and I opened it and found the above files but
I am so lost on what exactly to do next. Do I just copy and paste and put in my NI LV folder from my computer or do I do something else?
I also do not know how I can mass compile directories.
Does anyone have an idea? If you can give a detailed description I will very much appreciate it.
xxxMidna19
Solved!
Go to Solution.

Midna19 wroteo I just copy and paste and put in my NI LV folder from my computer...?
Yep.
To mass compile, to go Tools->Advanced->Mass Compile. Choose your directly and run the mass compile.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

Report Generation Toolkit Excel errors and Libraries, Classes

Hello All,
I'm using the Report Generation toolkit Excel functions to handle some data and create graphs. I'm running into problems with the Add Worksheet.vi. At the very start of the vi, it closes the reference to Shapes. Occasionally, the Close Ref will throw an error. I haven't pinned down the exact cause yet (probably an invalid reference). The error itself wouldn't be a problem. Under other circumstances I would choose to ignore it and continue on. The problem is, this is stored in a Class Library controlled by NI.
Solutions I've tried without success:
1.) Make changes, and save the new vi with another name - can't do it because it's encapsulated and the Library is password protected.
2.) Install toolkit in something other than the default folder, so I can make changes and put it under Source Control - installer doesn't allow a new path to be entered.
3.) Change the vi where it is. This works until I move the source to another computer or I update Labview. At that point I lose all my changes.
Maybe it's just my inexperience with Classes, but I just don't see an elegant solution to this. Ultimately I'd like to copy the library off to somewhere else and put it under Source Control so I can make changes and additions to it (NI folks - providing a password to unlock the lib would be helpful...). Does anyone have suggestions on how I can accomplish this?
Thanks in Advance,
Doug

Hi Ben,
Sorry about the first post. After re-reading it, it sounds more like a frustrated rant than a request for help.
I've attached a simplified vi to try to illustrate the problem I'm having. I'm running Excel 2007. Please open the vi, then open Excel Add Worksheet.vi. At the start of the vi, Close Ref for Excel.Shapes occasionally throws an error. So far, I have not been able to consistently reproduce the error, so I can't really troubleshoot it. As I recall, the error code is 1045. The error is carried through the rest of the vi, causing invalid references to be written to Excel._Worksheet and Excel.Shapes, going out to NI_report.ctl.
So, here are the issues I'm running into (other than the error itself):
1.)Short of closing and reopening the file, there is no way to recover from the error. After the error, there is an invalid reference in Excel._Worksheet. There is no vi available to regenerate references in NI_report.ctl. I could easily write a vi to start from Excel._Application and re-read them, but because NI_report.ctl is in a Class library (controlled and passworded by NI), I can't add the vi to the library.
2.) I found that I could ignore the error by wiring around it. If I disconnect Error Out from Excel.Shapes Close Ref and wire Error In from Excel.Sheets.Count to the Error In of the Close Ref, everything works fine. Under other circumstances, I'd save this with a new vi name (because functionality changed) and continue on. But, because the vi is part of a Class library (controlled and passworded by NI), I can't do this. I can save the vi with the modifications (because Excel Add Worksheet.vi is not passworded), but if I pass the source off to someone else, they will have to make the same changes on their installation of the NI Report Generation Toolkit.
Again, I can't reproduce the error with any regularity. I've run the example vi I provided a few times and everything seems to work fine. If I come up with something, I'll repost. If you (or anyone) has an idea of what could be failing or if they've seen the problem, I'd appreciate a comment.
Thanks again,
Doug
Attachments:
Excel Fail.vi ‏15 KB

Report Generation Toolkit on Vista and Office 2007

Hi,
I am trying to install Report Generation Toolkit 1.1.2 on LabVIEW 8.5 on a computer with Vista Business and Microsoft Office 2007.
The installation is starting, but I am receiving a message saying that "Microsoft Office 2000 or later is not detected on the computer"
The installation stops and the toolkit is not installed.
What can I do ?
Tom

Tom SAVU wrote:
Hi,
I am trying to install Report Generation Toolkit 1.1.2 on LabVIEW 8.5 on a computer with Vista Business and Microsoft Office 2007.
The installation is starting, but I am receiving a message saying that "Microsoft Office 2000 or later is not detected on the computer"
The installation stops and the toolkit is not installed.
What can I do ?
Tom
The Report Generation Toolkit does probably not support Office 2007 yet. This is because the Office ActiveX interface used to change with each version and the Report Generation Toolkit comes with specific libraries for each of the Office versions it supports. With the wrong office version the Report Generation Toolkit VIs are normally broken and can't run without some more or less involved modifications.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Open vi error for report generation toolkt

Originally it works fine.
Now I upgrade to win7, LV9 and office2010.
To open the old program by 8.6.1, I reinstalled LV 8.6.1 and report generation toolkit.
But still got the error as attached.
Any suggestion, thanks.
Attachments:
ss.png ‏184 KB

1. MS Office 2010 is not yet supported, since it's still just a beta. I believe there are couple of changes that Microsoft make, and it could cause a problem.
2. LabVIEW 8.6.1, and all its toolkit is not supported on Windows 7. This could cause a problkem also.
In conclusion, you should use LabVIEW 2009, Report Generation Toolkit 2009, Windows 7, and downgrade office to XP, 2003 or 2007.
More information: http://digital.ni.com/public.nsf/allkb/C9408B9F08D711E786256F3300701D01

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: New Report.vi

Running applicaion in development mode works fine.
After compiling however I get Error 7: Open VI Reference in New Report.vi
Why am I getting this error?

Has the version of Office on your machine changed since you installed the Report Generation Toolkit? The VIs will become broken if the ActiveX interface changes, and this can happen when the Office version changes. I recommend uninstalling and reinstalling the toolkit. Also, what version of Report Generation Toolkit are you using? The latest version is 1.1.1.
-D
P.S. - I'm going to respond to your other thread that you started with a link to this one. Instead of creating multiple messages on the same question, just wait for a response to your initial thread.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Report Generation Toolkit Error (undefined erro)

Does anybody know what error -214 682 7864 (0x800A01A8) means when coming from the Report Generation Toolkit.
I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet. The error was generated all the way down in NIReportGenerationToolkit.lvlib:Excel_Get_range.vi (this is the ActiveX code).
Any ideas?
nrp
CLA

nrp wrote:
I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet.
Was it the first time you attempted to write the table to that spreadsheet?
Maybe the error is due to the spreadsheet grown oversize than its limit so that it cant accomodate the table anymore.
What is the version of MS Office you are using? I think Office 2003 can go only upto 1024 columns...
- Partha
LabVIEW - Wires that catch bugs!

Report Generation Exe Error

Hello,
I am using LV 8.6.1 with the 1.13 report generation toolkit and I am having problems getting my built exe to work. I am trying to open an excel template and populate it with new data. I have broke the vi down to just opening excel - opening the template and then fill in some data. But at this point excel does not open at all. And naturally everything works fine in the development environment.
Error Code: -2147352573
Member not found in NI_ReportgenerationToolkit.lvlib:
Excel_open_workbook.vi
NI_Excel.lvclass: new reportsubvi.vi
I read a few help pages that said to add \vi.lib\utility\NIreport.llb and LVclass directories to the project folder and add them to the always include section of the build. But no luck so far.
Side question: The machine I want to use this on has 8.6.1 Full which does not have the extra excel functions that my developer has. Is there a way to install the DEV report generation toolkit in the full version? Then I would not need to build an exe.
UPDATE: I just tried the exe on a different machine that has a developer suite installed and it worked fine. So I guess I need to find out what else I need to add to the build to make it work.
Message Edited by _Bryan on 06-16-2010 11:58 AM
Solved!
Go to Solution.

There should be some info on this in the KB.
But first you should make sure that your version of the report generation toolkit actually supports excel 2000 (which is 10 years old)
That should be in the release notes of the toolkit
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Report-generation vi problem

On a Windows XP system using the "Text Report Example" vi, the (read) report property node item "TextFont" (stdole.Font) at the beginning of the "Font Style" vi which is a part of the "Set Report Font" vi is returning this error:
"-1073741819 Unknown System Error in Font Style.vi->Set Report Font.vi->Easy Text Report.vi"
Any suggestions as to a cause and cure?

This Knowledge Base from NI's website actually deals with this problem. The fix depends upon whether or not you have the Report Generation Toolkit for LabVIEW. There are fixes for whether or not you have the Toolkit. Hope this helps.
J.R. Allen

Report Generation for Excel does not work after using the Application Builder

I have a VI that writes data to an Excel file using the Report Generation Toolkit. I recently compiled the VI into a single Application (EXE) using the Application Builder. My VI runs its tests properly, but no data is written to Excel. What could be the cause? I don't receive any error messages.

Hi
I usually build exe-files, which sometimes also have report functionality.
Open the Application Builder and check the following things:
1. Add the following vis: _Word Dynamic VIs.vi, _Excel Dynamic VIs.vi They should be located in the directory ..\LabVIEW X.X\vi.lib\addons\_office in the llbs _wordsub.llb and _exclsub.llb (report1.jpg)
2. If you use an Installer, go to the Advanced Settings. There you can select some things to include in the Installer. Check if "NI Reports Support" is selected. (report2.jpg)
These are the things I always do, if I need reports and I never had problems up to now. I made two screen-shots of these settings.
Hope this helps.
Thomas
Using LV8.0
Don't be afraid to rate a good answer...
Attachments:
report.zip ‏25 KB

Report Generation Toolkit producing error -2147417842, "The application called an interface that was marshalled for a different thread."

Hi everybody,
I've got an application that logs data to an Excel spreadsheet using the Report Generation Toolkit. My VI's have worked fine in the past using Excel XP, but since I've upgraded to Excel 2007, I am getting COM errors like this one:
"Error -2147417842 occurred at The application called an interface that was marshalled for a different thread. in Excel_Insert_Text.vi" That is the exact wording, even with the weird punctuation and capitalization.
The first occurrence of the error is not determinate. Sometimes, up to 10 logging sessions, involving a new .xls file, can occur before this error pops up. Once this error occurs, I must quit LabVIEW to resolve it. If I try to do anything with Excel, I always get this error, although sometimes it comes out of different source VIs. Excel_Open.vi is another.
These logging VIs have worked just fine until upgrading to Excel 2007. I checked, and I was using a really old version of the Report Generation Toolkit, v1.0.1. I read the documentation and had a big sigh of relief when I realized I needed to upgraded to v1.1.2 to get Excel 2007 support. However, even after upgrading, I'm still getting the same errors. I'm using LabVIEW 8.0.1, and I'm also building these VIs into an application. The error occurs both in the LabVIEW IDE and in the built application. Does anybody out there have any idea what I can do to fix this? I googled a little, and discovered this is a COM error, but I can't find any references to the Report Generation Toolkit specifically.
Thanks,
Phil
Solved!
Go to Solution.

Hi Christian,
I do not see that exact option listed, do you mean "user interface"? I recognize the "Run in UI Thread" option, it's on the Call Library Function Node.
I checked, and my top-level VI has "same as caller" set, and I believe all my VIs are set to "same as caller". Are you suggesting I change my top-level VI preferred execution environment to "user interface", or just the logging sub-VIs that use the Report Generation Toolkit?
Thanks,
Phil
Attachments:
VI_properties.png ‏15 KB

Report generation for FPGA VI

Hello..
I want to include the number of resources used by FPGA (LUTs, slices, blockrams etc) in my report generation.
After compilation is completed, a window showing these resources will occur. But, how can I add this compilation report in my report generation...
Please let me know..
Thanks
Prashanth
Solved!
Go to Solution.

Hi
I made a small code which helps you achieve this functionality.
Hope it helps!
In this code: I read from "toplevel_gen_xst.log" file generated for the project; search for the string "Device utilization summary" and extract the part of interest Now you add this extract to your report compiled using report generation toolkit.
regards,
Ravi.
Attachments:
image.jpg ‏60 KB
FPGA Utilization.vi ‏10 KB

Report generation toolkit VI error when running EXE

A VI inside the Report Generation Toolkit (version 1.1.2), Excel Find Application Directory.vi, will not function correctly when running an EXE. The "Current VI's path" block will return the path of the currently running EXE rather than the path of the Excel Find Application Directory VI. (The same would be true for Word Find Application Directory.vi.)
-Joel
Solved!
Go to Solution.

Have you had a look at this knowledgebase article? The error is caused due to the exclusion of any dynamic VI.
Ipshita C.
National Instruments
Applications Engineer

LabView Exe Application file not launch Excel application for report generation

Dear All,
I created one LabVIEW application file for report generation (using Excel Template).
While I run the program in programming mode it works well and create the report file in the specified path.
After creation of the application file(exe), it gives the correct path of where the excel template is placed. The same path is given to New Report.vi, but it gives the error 'File Not Found'.
Tell me, is any other configuration required for generating Excel reports? (During exe application mode)
Give me the solution.
Thank You
Jegan.

Hello,
Most likely you are encountering a problem of stripping and/or building paths. Probably the easiest thing to do is put a couple indicators on your front panel for the path or paths you care about, build your exe, and make sure you are really using the path you'd like. If you always put the report at some deterministic place relative to the exe (that is, even it the exe is moved, it will go with the exe and remain in the same relative path location, then you can use the Current VIs Path funtion found in the ... File I/O -> File Constants palette as a start path (where you will want to strip at least the exe name off of course).
I think this will bring some clarity to the issue!
Best Regards,
JLS
Best,
JLS
Sixclear

Using remote machines for report generation

Since LabView does not have cross-platform openoffice support, I was looking at ways of generating reports from a LabView session (2010) running on a mac. The report generation VI contains a somewhat suggestive machine name input. Can one connect to a remote machine (which is windows XP and has microsoft word / excel installed) to generate reports from a mac running LabView ?

m-s wrote:
Since LabView does not have cross-platform openoffice support, I was looking at ways of generating reports from a LabView session (2010) running on a mac. The report generation VI contains a somewhat suggestive machine name input. Can one connect to a remote machine (which is windows XP and has microsoft word / excel installed) to generate reports from a mac running LabView ?
With some work I think is is do-able.
If the PC had an exe deployed and running that was served via VI Server the report could be run and generated on the PC when invoked from the Mac.
So in theory yes!
Edit:
VI server is not required if the exe on the PC listens at a TCP/IP port and supports a protocol to accept the report "job".
I'll watch to see (and in hopes of) a better solution form others.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Report Generation libraries

Similar Messages

Maybe you are looking for