Report generation toolkit upgrade issues

I have created multiple vi's in that utilize the previous report generation toolkits specifically using the Generate Report Get Data to Modify.vi and the Generate Report Set Modified Data.vi. Obviously the report reference has now changed in 8.6's version of the report generation toolkit and these vi's do not exist in the 8.6 library anymore. What vi's do I need to replace these functions with to make this code work. Can anyone tell me what the work around is to solving this problem. This is a picture of the code.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor
Attachments:
code.JPG ‏92 KB

Hi BJD1613,
The Report Generation VIs on the LabVIEW Palettes mutate properly. However, you may run into upgrade issues if VIs distributed with LabVIEW, but not available in the Palettes are used in the code. Hence, I would caution against using them for the same reason.
In this case, the specific references do exist in the report generation classes; however, since they are private, they cannot be accessed by VIs outside the respective classes. A temporary workaround for now is mentioned in the following KB 4OOCSJ4M Getting References in Report Generation Toolkit 1.1.3 with LabVIEW 8.6.
This was reported to R&D (CAR# 123064) for further investigation

Similar Messages

Report generation toolkit (1.1.2) and 8.5

I am not as crazy as I thought!
I wrote a program today that collects data from excel reports in many directories using cell names and it worked well. Unitl I saved it. I had been saving the sub vi's, but when I went to close them I got a message about unsaved changes and I guess I clicked to save the changes today. The program never worked the same again. I would get errors like 41106 and 41110 at random (problems with excel not opening and other stuff). I tried adding waits which slowed everything down and worked mostly. But the only way to not drop data and get errors was to have a copy of excel open while getting my data.
Well I just uninstalled/reinstalled the toolkit and rebuilt the vi that was having problems with the fresh install and everything is great again. So my question is why does the toolkit have problems when I save it in 8.5? The warning does say that the vi's are from 7.1 and I cant find any updates so I am hoping this is the latest version that came with my 8.5 suite.

Hi Bryan,
There should not be a problem with saving the VIs from the Report Generation toolkit in LabVIEW 8.5. I have checked the readme files to make sure but RGT 1.1.2 should work with any version of LabVIEW later than 7.0. However, the readme does discuss an specific upgrade issue. It says if you previously created VIs that use the built-in Report Generation VIs in LabVIEW Professional, Full, or Base packages or VIs from a previous version of the Report Generation Toolkit, installing the Report Generation Toolkit 1.1.2 might break the VIs you created. If the VIs you created contain any of the following VIs, edit them so they are compatible with the Report Generation Toolkit 1.1.2.
Append Front Panel Image to Report VI—The Image Format input of the LabVIEW 6.1 version of this VI is a different enumerated type than the current toolkit version. Right-click the input and select Create»Control or Create»Constant from the shortcut menu to create a compatible control or constant.
Append Table to Report VI—The connector pane position of the show grid lines input changed from the Report Generation Toolkit 1.0.1 version of the VI. Reconnect the original wire to the new input location.
Get Report Settings VI—The cluster order of the font settings input changed from the Report Generation Toolkit 1.0.1 version of the VI. Right-click the output and select Create»Indicator from the shortcut menu to create a compatible indicator.
Report Express VI—If a VI includes the LabVIEW built-in version of the Report Express VI on the block diagram, the VI breaks after you install the Report Generation Toolkit 1.1.2. Double-click the Report Express VI to launch its configuration dialog box, then click the OK button. Reconnect all wires to the Report Express VI.
You might need to relink the following subVIs after installation because the connector panes changed in the Report Generation Toolkit 1.1.2. Right-click the VIs and select Relink to SubVI.
New Report
Dispose Report
Append Front Panel Image to Report
Append Hypertext Link Anchor to Report
Append File to Report
Append Horizontal Line to Report
Set Report Font
One thing that might have happened is if you had created the program in an earlier version of the toolkit, then saved it in the new version of the toolkit, maybe some of the upgrade issues regarding the VIs listed aboved cause LabVIEW to start giving you errors. Also, which version of excel are you using? After you re-did the VI program, have you tried to save it again and see if the same problem occurs?
Carla
National Instruments
Applications Engineer

Report Generation Toolkit Table Row Height-MS Word

I am having trouble setting the table row height in the report generation toolkit. I can set the column width fine, but the row height seems to remain the same no matter what I set it to. I have attached the VI that generates and formats the table, and the printout it is resulting in. I have also attached the template file I am using.
Any tips to get this to work right? I am trying to make the cells exactly the same height as the text inside.
Solved!
Go to Solution.
Attachments:
AddMarkersToReport.vi ‏20 KB
badFormatting.pdf ‏179 KB
splitter.docx ‏13 KB

Hi,
So I tried .2 and it didn't work. So I went to Word to manually change it, and it did not work either. There is a selection box in word, for the table properties, that seems to default to the value "at least". When I changed this manually to "exactly" in word, no problem with the .2 manually in Word.
Hopefully this can be set within the template, for all new inserted tables. I'm not sure the report generator VI's expose this property. Well, this is a start for the issue.
Edit ****
You can go into the add table VI and expose the property. See pic. However, you have to decide if you want to "upgrade" this VI permanently to expose this property or make a copy with the property exposed. I haven't messed with the new class reports too much, so not sure of the ins and outs with this.
I think this is the issue with the row size becoming smaller.
Mark Ramsdale

Suggestion about Report Generation Toolkit

I'm adding report generation capabilities to a labview product test application. The report will be 2-4 pages long with text and plots. For other applications, I've used Word Templates in the past using VBA and Visual Basis 6. I had been planning to use the Report Generation Toolkit, but when I tried to run the examples Labview doesn't find the installation of Office, (I'm using Windows Vista). I've already read other posts about this particular problem and other issues with the Report Generation Toolkit for Microsoft Office, including upgrading to Office 2007 and beyond and I'm beginning to wonder if there might be a better longterm solution than the Report Generation using Microsoft Office.
The two alternatives that I'm considering are HTML, and Simplicity AI's PDF toolkit (free),
http://www.simplicityai.co.uk/products_services/products/pdftoolkit/
which I still have to investigate. I figure I could always generate in HTML and then print to PDF using something like PDFcreator (free).
If anyone has any comments/reviews/suggestions about the report generation from Labview, I'd appreciate hearing them.

Hello PointOnePa,
What examples were you trying to run? Here's a good example on how to create report in Excel
http://zone.ni.com/devzone/cda/epd/p/id/1001
Which version of LabVIEW and Report Gen you do you have? For Reort Gen 2009, it offers support for MS Office 2007/2003/XP
http://digital.ni.com/public.nsf/allkb/45E349F79A55EAE6862575EF00614134
Andy Chang
National Instruments
LabVIEW Control Design and Simulation

NI report generatation toolkit upgrade

Hey there,
I have some old VIs that used to be in the report generation toolkit(1.0.x) I need to modify and upgrade.
Generate Report Set Modified Data.vi
Generate Report Get Data to Modify.vi
Generate Report Get Data.vi
seem not to exist anymore in the labview 2011 report generation toolkit.
I can grap an old library that I have on another PC that includes those missing VIs but then I have an issue with
Generate Report objectrepository.vi that is password protected and not executable.It prevents those VIs from execution.
Found some NI froum discussions from years ago on Ni forum and a link from NI website but could not find any viable solution yet. http://digital.ni.com/public.nsf/allkb/0C7100D6E9E4783B862575070055A499
I just wonder if there is anyone who already modified some VIs probably with the new activex calls to replace with those missing vis and managed to make the update successfully?
Solved!
Go to Solution.

I was able to hear back from back from NI R&D about the difference's between the Report Generation Toolkit
(RGT) and its references. While the intent was not to break any old code, they did decide to change to a object-oriented approached for the RGT. The RGT references have been changed to lvclass type instead of refnum, and it does not look like there is a conversion.
As for the NISH Report, it is provided so older applications do not break, but they still recommend converting your application to the newer VIs for the future. We do not seem to be able to find any documentation on the NISH Report library though, so I would still reference your old help documents when using it. R&D did say that the VIs should work for Office 2007 and earlier.
Since our application used standard report generation toolkit and ended up with .csv file I just used my own library within my new labview 2011 sp1 application(with each vi and ctl names uniquely assigned as they get mixed up with new RGT) created from RGT vis for labview 6.1 except the broken and password protected vi `generateobjectrepisotory.vi` that you can now find the working revision under NISH.lib.
This solution worked for me. Hope it helps you.

LabView database connectivity toolkit 1.0.1 compatibility with MS-ACCESS 2010 / Labview report generation toolkit for Office 1.1.3 compatibility with Office 2010

In the very near future we will be forced to upgrade to Office 2010 Company wide and I am a little concerned with some of our older test platforms that have applications built in LabView 8.2.1. These applications save data to MS-ACCESS 2000 databases using the LabView database connectivity toolkit 1.0.1. Office 2003 is also loaded on these test platforms with all test reports generated using the LabView report generation toolkit for Office 1.1.3.
I have not gotten my hands on a copy of Office 2010 yet to see if there will be any compatibility issues. Does anyone have any experience in this area?

The MS-Access part is fairly well isolated through the ADO interface LabVIEW uses. The only possible problems there IMHO are difficulties with possible Acess compatibilities itself such as an example, SQL statement you may have invoked directly through the ADO interface. Maybe you did use a depreciated command back then that has since been removed. As long as the only thing you do are simple INSERT and SELECT statements only, I would expect it to just keep working.
The Report Generation interface is a different beast. Microsoft manages to change the Automation interface with every version of office in a way that strongly binding applications like LabVIEW break on. There is no good way around that except not changing those methods, but that is a cause that has been lost already. You will certainly have to verify the version dependant Report Generation API VIs to still work with Office 2010 and most likely you will have to make some changes to those VIs to make them work again with the modified ActiveX interface of Office 2010. Note, that I have no experience with porting report generation to Office 2010 but I have had some headaches from porting that between Office 97, 2000, 2003, and 2007.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

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

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 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 missing VI

LabVIEW version 8.6.1
Report Generation Toolkit 1.13
I have just started work on an ongoing project that others have been contributing to for some time. (Hence the project being in older versions of LabVIEW)
On my PC, I am apparently missing the VI "Word Get ActiveX References.vi"
I do have the version 1.13 of the toolkit installed, just as every other machine that runs this code does. But my word.llb does not contain that VI
I have tried simply copying that VI into the .llb The VI is then found by the application. But is not executable due to this error: This VI is connected with a library that does not include the VI. The VI might have been deleted from the library. Add the VI to the library again or select File»Disconnect from Library.
I have also tried replacing my entire C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\addons\_office\ directory with files from a PC that was working. Again, I get the same error as above.
I did attempt to do a repair on my installation of the toolkit. But as far as I can tell, this didn't do anything.
I also tried simply reinstalling the toolkit. But since it was already installed, it did nothing. I am hesitant to uninstall and reinstall the toolkit for fear of breaking all of my 8.6 projects, as well as possibly my 2009 projects. I wouldn't think it mess with my 2009 installation. But I do know that the order in which things are installed can be critical in system with multiple versions. I'm not sure if this applies to toolkits or not.
This PC also has an installation of LV 2009 SP1, and that version also has the Report Generation Toolkit installed. (although it is a different revision of the toolkit than 1.13)
I know that in the past, multiple versions of this toolkit were not compatible, meaning only one installed version of LabVIEW could have a working Report Generation Toolkit installed. But I was of the understanding that this was no longer a problem. Although it may not be a coincidence that neither of the other development boxes running this code do not have LV 2009 installed.
Has anyone else ever run into a similar problem and found a solution?
Thanks.
Patrick Allen
Solved!
Go to Solution.

Darren wrote:
Back before we unified the LabVIEW and toolkit version numbers (in 2009), there were cases where we didn't change the version number in the registry for one reason or another on a minor upgrade.
Ah. This makes sense then.
I just reinstalled said toolkit from said SSP DVD and although it did tell me that I was about to install 1.1.4, MAX still thinks it's 1.1.3
...except that now I do have the missing VI. This is a good thingTM
I still wonder how it ended up missing, because I'm really sure this is where I installed the toolkit from in the first place. I'll probably never know for sure. But that's a lot easier to take when the code is working.
Thanks!
Message Edited by pallen on 04-15-2010 04:52 PM
Patrick Allen

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

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

LV 2011 Report Generation Toolkit Constantly asks for 8.6.1 CD

I am having a strange issue.
Its a bit intermittant, so I will try my best to explain when it occurs.
-If I make a new project and run something from the report generation toolkit, I will get an installer from labview 8.6.1. I am running Labview 2011 and have never had 8.6.1 installed on this computer. It will spend about 3 minutes installing something, then demand a labview 8.6.1 CD.
-If I hit cancel it goes away for the project, until I restart the computer. It does not actually need the CD, it just asks for it. The VI containing the report subvi will execute fine, but if I open any of the front panels I get the installer message again.
-If I have run something that uses the report generation toolkit previously in this login session I do not encounter the bug.
-Restarting labview does not make it appear, only restarting the computer
Solved!
Go to Solution.

There are classes in the RGT that are loaded dynamically. You need to include the VIs in your build.
We found you should add the following two folders to your project and then force them to be in your EXE build.
<LabVIEW>\vi.lib\Utility\LVClass
<LabVIEW>\vi.lib\Utility\NIReport.llb
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Report generation toolkit upgrade issues

Similar Messages

Maybe you are looking for