Report generation toolkit jumping between workbooks

Hi,
I am having an issue with my VI which I am wondering if anyone has a fix too or workaround.
Basically during my tests I write multiple sets of data to different sheets in Excel using the Report Generation Toolkit.
At the start of my code I open a workbook (template Excel file), I write data to the file at the end of each test for each iteration and then save and close the file at the end.
I have attached a PNG of one of my sub VIs which writes one set of data to one sheet, this could be called numerous times during my code.
The issue I have is that if I am working with a seperate workbook, each time my sub VI runs it will jump to the test results workbook.
I am aware that I do "Get" the workbook in my code and this is why it happens.
Is there a way to call different sheets in a workbook in a VI without affecting the user who is working on a seperate workbook, write data in the background?
I am unsure if it is possible to write data to different sheets in a workbook without using the "Excel Get Worksheet VI" before entering the data.
I also know I could just save all data in arrays and then at the very end write all data to the workbook but this is not a preference
Any information would be gratefully appreciated
Thanks.
Solved!
Go to Solution.
Attachments:
write_to_excel.PNG ‏14 KB

Changed the window state to "No Change" in the new report VI
Seems to have done the trick
Attachments:
report_settings.PNG ‏2 KB

Similar Messages

Difference between diadem and LabVIEW Report Generation Toolkit

I want to expand LabVIEW's reporting capabilities. Can someone tell me what the difference is between DIAdem and the LabVIEW Report Generation Toolkit for Microsoft Office.

Hello Mr Bean,
There are several major differences between the two solutions. I'll try and outline them as good as I can ...
The biggest different is that LabVIEW and its toolkits are programming tools and DIAdem is a ready to run application.
The LabVIEW Report Generation Toolkit basically provides an extensive library of VIs that allow you to connect LabVIEW to the MS Office library and create and edit reports in Word and Excel.
DIAdem is a stand alone application that was designed to post-process data from various sources. The tools included in DIAdem are:
1. NAVIGATOR: Allows you to import data from files (ASCII, binary, Excel, etc.) as well as DataBases (SQL/ODBC, Citadel, ASAM, etc.). The unique DataPlugin technology available within DIAdem allows you to import vitually and data file by creating a DataPlugin that describes the data format and gets linked to DIAdem. More information at: http://www.ni.com/diadem/dataplugins.htm
2. VIEW: Graphical and Numerical data inspection tool. Use cursors to zoom and scroll through your data, edit your data graphically and numerically and compare different tests.
3. ANALYSIS: DIAdem has a wide range of analysis functions, ranging from simple functions like integration and differentiation to FFTs, Order analysis and 3D data analysis.
4. REPORT: The DIAdem REPORT tool allows you to create reusable report layouts that can contain multiple axis systems (2D, 3D and polar plots) as well as tables (2D and 3D) and variables. The REPORT tool generates templates that can be usedwith multiple data sets due to the inclusion of automatic (or manula if required) scaling as well as extensive use of variables for annotations. Finished reports can be exported to printers, graphics files, the Windows Clipboard, HTML pages and PDF files (PDF writing is build into DIAdem, no extra software required). Using Scripts, it is also possible to create Word, Excel or Powerpoint reports from DIAdem automatically.
5. SCRIPT: The DIAdem scripting tools allows users to record macros or write scripts that automate complete sequences, for the import of data, via extensive analysis, to creating a publication ready report. Scripts can make reports "intelligent" by modifying the appearance of a report based on the data or calculation results that are going to be displayed in the report.
I recommend you check out the following link for more information: http://www.ni.com/diadem/
DIAdem is an extremly powerful tool for report generation. I am leaving to go on a business trip to Asia, but I would be more than happy to give you an Web presentation on DIAdem after I have returned. We could use your data and create a DIAdem report Script together online. My Email address is [email protected] and I will be back the week of Thanksgiving.
Otmar
Otmar D. Foehner
Business Development Manager
DIAdem and Test Data Management
National Instruments
Austin, TX - USA
"For an optimist the glass is half full, for a pessimist it's half empty, and for an engineer is twice bigger than necessary."

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 and Office XP and 2K

Hello Everybody
I am having few problems with running executable using Report Generation Toolkit on machine with Office 2000, which was compiled and build on machine with Office XP (toolkit also XP).
There are many errors which pops up, but the very first one is that the "New Report.vi" can not open the existing Excel book.
Is there any trick, which allows machines with Office 2k to run application build with Office XP?
Thanks in advance.
Pawel

Hi Cin
Yes, that is correct. The reason why I ask was how to find a solution so both XP and 2k can work in the same time.
You are right that most of the features for XO and 2k are simmilar, but try to use XP to open w 2k workbook from excel, it will fail.
cheers
Pawel

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

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

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

Remove worksheet VI - Report Generation Toolkit (LabVIEW 8.6)

Hello,
I am using the Report Generation Toolkit that ships with LabVIEW 8.6 for creating an Excel report. I am looking for a way to delete spreadsheets in a workbook. I did come across couple of message posts in the forum which mentioned about worksheet removal using some VIs that were shipped with previous version of LabVIEW. I could not find the built-in VIs in newer version of report generation toolkit (the one with LabVIEW 8.6).
Is there a way I could remove worksheets in LabVIEW 8.6?
Thank you.

Assuming you're using Report Generation Toolkit 1.1.4 with LabVIEW 8.6, you can use the following VI (in the Report Generation > Excel Specific > Excel Advanced subpalette) to gain access to your current Worksheet and/or Sheets object:
Note that this VI is not available in Report Generation Toolkit 1.1.3.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Print number of pages with Report Generation toolkit

I use the report generation toolkit and the Print Report.vi to print a table and some text extracted from a MS Access database. The result of this is a print out that takes up several pages.
Now, on each page i want something like (Page x of y), and I do not want to buy more expensive NI packages for this simple thing. I know it should be possible since the Report Express vi can do it --- which for me is a useless vi.
I do not consider it a nice solution to try and keep track of the number of pages myself by dividing the table into more tables and use the new page vi between each "page table". This I would not like to do since depending on paper size, font size, and length of text strings in each cell this will be virtually impossible.
By moving into the Print Report.vi I've tried to see if I somehow can extract the info --- I've not found anything usefull but expect a workaround to possible.
Any suggestions?
Cheers,
Martin

Hi Skinny,
There are some tokens you can use in the headers and footers of Standard Reports generated by the Report Generation VIs. If you take a look at [LabVIEW]\examples\reports\TextReportExample.llb\Text Report Example.vi, you'll see that the right footer text of the report has the token <pagenofm>, which generates a footer of the form "1 of 10", to indicate page 1 out of 10 pages. There's also another tag you can use, <page>, that just lists the page number itself without a total number of pages. If you look at the help for the Set Report Header Text.vi or Set Report Footer Text.vi, you'll see a link in the help for all the different "tokens" you can use with the report header and footer. Actually, now that I think about it, you can use these tokens anywhere in the report, including the body text.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Can i open a existing report using a report generation toolkit

Hello All,
Suppose I create a new excel report today and close the program, Tomorrow I open the same program and instead of creating a new excel file, i need to update the test results data into the excel file which was created yesterday, is this possible.
I am confused because there is no option called Open report in report generation toolkit, it just has create new report option.
Probably NI Guys can work on this...sorry if it is a;lready existing?
Is there any method to open a existing report?
Pls help.....
Thanks
Solved!
Go to Solution.

Hi,
I have a similar problem. I'd like to use Report Generation Toolkit to enter data into some cells in the active worksheet of the active workbook but it seems impossible?! The user has in beforehand opened the desireed workbook and activated the desired worksheet. I use the 'New Report' VI with the template input set as the path of the active workbook (some self-made ActiveX calls to get the path). When this VI is run, howevere, the excel file is sort of re-opened and another worksheet becomes the active one.
I tried to make a customized copy of New Report.vi, New Report subVI.vi and Excel_Open_Workbook.vi so that the Report object works with the currently active workbook and worksheet, but I failed due to my lack of knowledge in LV classes and such things. It would've been an ugly solution anyway to have custom low-level VIs that does not follow when the RepGen Toolkit develops in the future.
Best regards,
Andreas Nilsson

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

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

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

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 jumping between workbooks

Similar Messages

Maybe you are looking for