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

Similar Messages

  • Report Generation Toolkit labview 2013 64bits?

    Muy buenas tardes.
    Estoy buscando el Report Generation Toolkit para labview 2013 64bits, lo he buscado pero no logro encontrarlo y con este mismo pero de 32 bits me marca error al instalarlo.

    Hola Antonio,
    Intenta con esta liga : http://www.ni.com/gate/gb/GB_EVALTLKTREPGEN/US
    Espero que por aqui lo puedas descargar,
    saludos
    Erwin Franz R.

  • Is it possible to insert data into two Excel worksheets using Report Generation Toolkit?

    I'm using the toolkit to insert data into two separate worksheets in Excel using named cells. The problem is that it tends to favor one sheet or the other. In other words, one sheet will have data and the other no data and vice versa. (Sometimes I get data in both sheets.) Is there something I can do to clear this up or is what I'm trying to do unreasonable? I would like to use two worksheets so one sheet receives text and data. The other sheet is used to format the data into a printable report. (i.e. using Excel's CONCATENATE function) The second (report) sheet is also used to receive plots (JPEG files) from LabVIEW. I'd send the plot images to the first sheet, but I can
    not see a way to automatically transfer images from sheet to sheet. I'm using LV 7.1, Win2000 and Toolkit v.1.0.1

    Hi,
    You can use the "Excel Get Worksheet.vi" under All Functions >> Report Generation >> Excel Specific >> Excel General to specify a particular worksheet as the current worksheet. Then, you can specify which worksheet you want to write to in your VI.
    Let me know if you have any further questions and good luck!
    Kileen C.
    NI

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

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

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

  • Problem with Reporte Generation Toolkit for Microsoft Office 2010

    When I use the Report Generation Toolkit (LabVIEW 2010), and Office 2010,  the tables generated are bad.
    In office 2007 in the tables are correct.
    Someone can help me solve this problem?

    The solution referenced in your post does not actually workas far as I can tell... at least for LV2011 and Office2010 on Win7
    Am I missing something here?
    Attachments:
    Testbench_ReportGen Table_BUG.vi ‏10 KB

  • Report generation toolkit: Get all excel worksheets

    Hej everybody,
    how can I get a list (name and number) of all worksheets in an Excelfile using the report generation toolkit and Labview 8.2?
    Thanks for answers,
    Christoph

    Hi,
    I made the similar application using excel dll in LabVIEW 7.1 
    Try this...
    Regards
    DC
    Attachments:
    Excel_Worksheets.vi ‏48 KB

  • Report Generation toolkit for labview 2010

    H All.
    I'm looking to download the report generation toolkit for labview 2010. When I proceed to download the toolkit from the national instrumnets website, it says that i need to labview 2011 or later in order to install it.
    Is there a version of this report generation toollkit for labview 2010 and can someone provide a link maybe??.
    Thanks for reading.
    Solved!
    Go to Solution.

    Try this: [Link removed, NI software downloads can be found on ni.com/downloads, the LabVIEW 2010 Report Generation Toolkit is available to customers with Standard Service Program here: http://joule.ni.com/nidu/cds/view/p/id/3247/lang/en, other customers may contact NI directly]
    Beginner? Try LabVIEW Basics
    Sharing bits of code? Try Snippets or LAVA Code Capture Tool
    Have you tried Quick Drop?, Visit QD Community.

  • Labview 2013 report generation toolkit word 2010 insert table problem

    Hi,
    I am currently evaluating LV2013 with respect to the report generation toolkit for use with word 2010. My Vi/program won't insert the correct table and gives me an error message. see below:-
    Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table​.vi->NI_Word.lvclass:Append Text Table to Report.vi->Word Table save.vi
    I have since run the following word example.vi provided by NI within LV2013 office examples:- Growable table.vi. this gives me the same error!
    Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table​.vi->NI_Word.lvclass:Append Text Table to Report.vi->Growable table.vi
    It would seem that regardless of my own Vi there is a fundamental problem in the office example vi.
    I have found examples of a similar problem in LV2011/2012 but the work around code doesn't seem to match the LV2013 vi's code for a direct replacement.
    Can anyone help/shed some light on this? 
    Thanks in advance,
    Dan.

    Because the upgrade of Word from 2007 to 2010 I needed to upgrade an existing application from LabVIEW 2009 to 2013. This didn't work because of the insert table error. I discovered that the problem is the vi called "Word_Insert_Table.vi" located in the ..Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\addons\_office\_wordsub.llb. There is a "Cut" command implemented, this command removes the created cell instead of clearing it. Therefore the table will be filled half and then returnes with an error. I have removed this command. I have posted the changed vi (LV 2013).
    Attachments:
    Word_Insert_Table.vi ‏30 KB

  • National Instruments releases LabVIEW Report Generation Toolkit for Microsoft Office.

    The new LabVIEW Report Generation Toolkit for Microsoft Office is a library of flexible, easy-to-use tools for programmatically creating and editing Microsoft Word and Excel reports from LabVIEW. Whether you need to generate reports summarizing manufacturing test results or compile process statistics to improve your production yields, this toolkit speeds your development of customized, professional reports.
    To see examples of this toolkit or get more information please visit :
    http://www.ni.com/labview/report_gen_toolkit.htm

    It is a bit limiting though. I built my own set of VI's, a toolkit if you will, that does some of what this tookit does. But, I also wrote some functionality that isn't available in NI's kit, such as creating charts as separate worksheets and linking the charts to data on another worksheet. All in all, the toolkit is great, but you can't get as much out of it as you can using the ActiveX calls yourself.

  • 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 (1.0) can't be installed under LabView 6.1.

    When installing the toolkit, it showed that it was unable to locate the LabVIEW run-time engine of version 6.0 or compatible. However, my computer has already installed a run-time engine 6.1 (I saw it on my control panel->Add/remove programs). Do I need to install another run-time engine 6.0?

    Hello William,
    You may want to see this article on NI.com. It sounds like it addresses your particular issue.
    Regards,
    Chris J
    Installation Errors with the Report Generation Toolkit 1.0 for Microsoft Office and LabVIEW 6.1
    http://digital.ni.com/public.nsf/websearch/BEE4820C6BB7305186256B42005C9514?OpenDocument

  • 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

  • How to obtain the table index in word use LabVIEW Report Generation Toolkit for Microsoft Office

    I created a word templete and it had several tables. When I use the "Word Edit Cell" function in LabVIEW Report Generation Toolkit for Microsoft Office, the function need "table index", and I didn't find any function to get or set the table index in word document. How can I achieve my attention to write value to specified table cell using the "Word Edit Cell" function?
    Thanks for reply!
    YangAfreet

    Hi yangafreet
    You do not need to get the table index for the word edit cell.vi from anywhere. LabVIEW will automatically index all the tables in the document. See the attatched vi for an example.
    Rich
    Attachments:
    Table Edit.vi ‏23 KB

  • 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

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

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

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

Maybe you are looking for