Old Report Generation Toolkit VIs

I have some old VIs I'm modifying and they, themselves, use VIs that used to be in the report generation toolkit but no longer are (Generate Report Get Data to Modify.vi, Generate Report Get Data.vi, show table lines.vi, etc...there are many more). I can grab an old library that I have on another PC that includes these VIs, but then that causes all sorts of conflicts. I have seen lots of things posted that are somewhat like this but no viable solution. Does anyone have one, so that I can load the VIs and not have to redo any code?
CLA, LabVIEW Versions 2010-2013

for(imstuck) wrote:
I have some old VIs I'm modifying and they, themselves, use VIs that used to be in the report generation toolkit but no longer are (Generate Report Get Data to Modify.vi, Generate Report Get Data.vi, show table lines.vi, etc...there are many more). I can grab an old library that I have on another PC that includes these VIs, but then that causes all sorts of conflicts. I have seen lots of things posted that are somewhat like this but no viable solution. Does anyone have one, so that I can load the VIs and not have to redo any code?
I believe that is yet anothe manifestation of the issue I posted about in this thread where using VI's that are not on the palettes, can sneak up and bite you when LV gets updated.
In the case of the DB and report gen tool kit, the first version re-written in LVOOP did not expose any methods to get at any of the classes agregated by the class (how is that for OOP speach?).
Latter version of those tool kits exposed the ref to the more advanced functions so first make sure you have the lateset and greaset version of the tool kits.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Similar Messages

Error Showing While Using Report Generation ToolKit VIs

Hi All,
           When I use report generation VIs Like Excel Easy Tables its showing following errors and i am not able to contiune using the same,
C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\utility\NIReport.llb\Set Report Font.vi
    - LabVIEW 8.0 changed a constant that was wired to a Case structure to a hidden control to maintain compatibility with LabVIEW 7.1 and earlier.
    - LabVIEW 8.0 changed a constant that was wired to a Case structure to a hidden control to maintain compatibility with LabVIEW 7.1 and earlier.
what might be the issue, i am using LabVIEW 8.2

Hi,
In
LabVIEW 7.1 and earlier, subVIs could be kept in memory by wiring a
constant to a Case structure and placing the subVI in a case that would
not be executed. For example, you could wire a True constant to the
Case structure and place a subVI in the False case of the Case
structure, and LabVIEW would load the subVI along with the calling VI.
However, from LabVIEW 8.0 onwards, the case structure is optimized to remove code that is not going to be executed. Changing the
constant to a control ensures that this VI behaves as it did in LabVIEW
7.1 and earlier. If the intent is not to keep the subVIs in memory, you
can change this control back to a constant by right-clicking the
control and selecting 'Change to Constant' from the shortcut menu. The
proper way to keep a subVI in memory without calling it is to use a
Static VI Reference.
Good Luck!
Warm regards,
Karunya R
National Instruments
Applications Engineer

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

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

Report Generation Toolkit doesn't work after patches A thru I.

For LV7 Express, RGT demo doesn't run any of its operations, Word, Excel,... See attach for cause. Can anyone tell me how to fix this?
Attachments:
RGDemo1.doc ‏36 KB

Hi,
When you get this error, it's normally because the version of the Report Generation Toolkit VIs in your VI that you are trying to open is different from the one on your PC. Normally you can just right click on the bad VIs on the block diagram and choose "Relink To SubVI".
There's a KnowledgeBase that describes another issue when using different versions of Microsoft Office.
Best regards,
Philip C.
National Instruments
- Philip Courtois, Thinkbot Solutions

Problems creating a web service that uses the report generation toolkit

Hi,
Im trying to develop a web service using labview 2013.
I create a html form that is correctly communicating with my labview method and part of the web service functionality is to create a report from the data obtained in the html form published.
I realized that using the report generation toolkit inside of the web service method the server cannot generate a report. ( If I run the same Vi before publishing the web service it works on the server but it doesnt work after I deploy it)
I thought that maybe Im unable to use the report generation toolkit VIs inside of the web service because Im not incluiding the (dynamic VIs labview uses when they run), I tried to add the excel dynamic library to the proyect but with no success.
I also tried to use VI SERVER to call a VI that generates the report using the report generation toolkit in the method that runs when the web service is call but it doesnt work either.
How can I deploy a web service able to use the report generation toolkit ?, how can I deploy a web service able to use VI server ?
Any help is really appreciated.
Erwin Franz
Erlab

The issue you are running into is actually a limitation intended by Microsoft. They don't want windows services to be able to call into the ActiveX interface for Microsoft Office for security reasons. If you are deploying your web service to the NI Application Web Server on Windows you will run into this problem since the web server is a Windows Service.
While I haven't tested this, you may be able to work around this by packaging your Web service with a LabVIEW EXE rather than deploying to the NI Application Web server.
Mark
LabVIEW R&D

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 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)

What is wrong with the report generation toolkit????

OK. Now I'm a little frustrated.
I started this thread, but then made an ugly workaround until someone tells me the correct solution.
So now.... my compiled application can find all the toolkit VIs... but I get error messages telling me that the VIs were are too old (V 7.0) to be recompiled to Version 8.5.1.
When I got the first of these messages, I opened and saved the VI indicated. That just pushed the problem along to the next VI. So I said "ah ha!" and went to the directory (blah\blah\....\addons\_office) that has the toolkit routines and did a Mass Compile. No errors were generated by this.
NOW when I try to run, I get an error message telling me that Excel_Insert_Text.vi is not executable. But that is clearly a lie. When I open the VI in the development environment, there are no broken arrows...
And let us not forget my application runs perfectly and without errors in the development environment, even after I brutally recompiled everything.
For those who care: I'm running V 8.5.1 with whatever version of the Report Generation Toolkit comes with that (1.1.2??).
Arrgh.
-GN

I feel your pain GN... the RGT in its current Classes incarnation has a few "issues"... try deploying it with TestStand a whole world of pain opens up.
Now, I have recently seen an issue very similar to the one you described, I broke the RGT after doing a mass compile.
Eventually opened the RGT VI that was "broken", it looked fine to me. It was something to do with setting the font, and was basically just an activex call. Eventually out of frustration I right clicked on the node, reselected the same method, and another input parameter line appeared at the bottom of the node and the VI all of a sudden became runnable. WOW!
This needed to be done in a few of the VIs.
Maybe this will help you
nrp
CLA

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

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

Problem for Report Generation Toolkit for excel 2000

Hi all,
Now I am Developing my program with Report Generation Toolkit 1.1.0 and Labview 7.1.
In my computer I am using Excel XP, and there is not any problem. But when I build to
a exe file, and use in a computer with Excel 2000, it didn't work.
And I try to check the source file in this computer, I found that there any some connection
error. And this is caused by the active X class. As I know Excel 2000 is using Microsoft Excel
Object Library 9.0, but i cannot find it in the list of active x. So it is using Microsoft Excel Object
Library with a very old verison. So in the property node there are missing functions, such as the
UsedRange in _Worksheet in the Excel_Get_Range.vi. However, In VBA, I can find the 9.0 Library.
Is it the problem of 9.0 library? How can I solve the problem? How can I upgrade the library to 10.0?
Thanks.
Regard,
Ryan

Hi Mike,
Since my program is for all the staff in office, everyone may use it.
I cannot call the whole office to upgrade the excel to XP.
And I think Report Generation Toolkit is alway support Excel 2000,
since the old version of it is not support for Excel XP.
Regard,
Ryan

Report Generation Toolkit Excel Vi's do not run after creating an executable. What am I missing?

I have labview 8.5 and Report Generation Toolkit version 1.1.2. My vi works fine during development. When I make an executable or an installer the excel vi's do not work. I have seen this question posted before but it has always been for earlier revisions and the answers do not seem to apply with 8.5 and 1.1.2.

Hello ajh,
You will have to include Dynamic VIs in the executable you build. The following link has more information:
http://digital.ni.com/public.nsf/allkb/C38CE3F30542D65B86256F0E00740DD8
Prashant.

Report Generation Toolkit files in incorrect location after installing deployment

TestStand 2010 SP1 + LabVIEW 2011 + Report Generation Tookit
After installing a deployment, the location of NI_Excel.lvclass is expected to be at ...\VIs for <project name>\SupportVIs\Excel\NI_Excel.lvclass (see attachment)
but the path of the file is located at ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
In the deployment image, under the target folder, the file is in ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
and the lvproj finds the file.
The lvproj in the installation finds the file in ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
Renaming the folder from data to Excel fixes this problem.
Has anyone else run into this problem?
Attachments:
Report Generation Toolkit Error.png ‏15 KB

I am facing the same issue when I create the TS deployment through utility using TS2012.I thought of adding the file to the Teststand workspace and give the destination in to supportVIs directory.But even tthat didn't worked as it was copying all excel vis in to two locations.
Even adding the Directory path in to TS search directory options to "\data folder" is not resolving the issue and LAbVIEW Vis are not able to locate it.

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!

Old Report Generation Toolkit VIs

Similar Messages

Maybe you are looking for