The version of Report generation toolkit

which version of Report Generation Toolkit is compatible to which version of LabVIEW?
I'm using LabVIEW 7.1

The latest version of Report Generation Toolkit 1.1.2 is compatabile with any version of LV 7.0+.
Warm regards,
Karunya R
National Instruments
Applications Engineer

Similar Messages

  • Opening Existing Word/Excel Files Using the LabVIEW Office Report Generation Toolkit

    Hi...
    Can anybody help me for opening an existing excel sheet with specified name
    Am using labview 8.0
    Thanks in advance...

    Chck out the examples that ship with LV. There are demonstrations of how to communicate with Excel. The only question is whether Microsoft has chnaged the ActiveX interface to Excel.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • LabVIEW VI with Report Generation Toolkit elements in a TestStand sequence does not run with a LabVIEW 8.5 Run-Time Engine

    Hi all,
    I am using LabVIEW 8.5.1 and TestStand 4.1. I have done a TestStand sequence with a VI in it, which uses Report Generation Toolkit elements. On my machine I am using LabVIEW and TestStand with a Development System license. On the other machine I am using TestStand with a Base Deployment license and I have chosen the LabVIEW 8.5 Run-Time Engine in the Adapter Configuration. Everything is running well except of this VI with Report Generation Toolkit elements. The error message is showing that the VI is not executable. It works well only after I have installed LabVIEW with an Evaluation license and chosen LabVIEW 8.5 Development System in the Adapter Configuration.
    I have found other posts and a document in the KnowledgeBase with a similar problem: http://digital.ni.com/public.nsf/allkb/8A0E6274D9B​D7B1986256F62006AD402?OpenDocument But I am not using EXE files in my sequence, so I don't know how to solve mine. Anybody has an idea?
    Solved!
    Go to Solution.

    Hello guys,
    thank you very much for your answers!
    @Ruediger:
    I tried to follow the instruction for Method 2 in the mentioned document: http://digital.ni.com/public.nsf/allkb/F3DC40A6E3F​3B25B862570AD005D1D3D?OpenDocument, but the steps on my machine are different starting from step 4. After I click "Continue..." in step 3, I dont get a window, the system just makes a new folder with the same VI. 
    To be honest, I am new to LabVIEW and have some difficulties at this time. What I understood from your reply is, that I need to make a LLB-File, where the files from Report Generation Toolkit are in!?
    @GovBob:
    I was following the instruction in the document: http://digital.ni.com/public.nsf/allkb/9E00E7EFE06​35E678625734600779EFE, but it wasnt working. Can you please tell me how I can check if the VI Server is installed and running on the machine?
    I am using LabVIEW 8.5.1 and TestStand 4.1 on my machine, on the deploy machine there is TestStand 4.1.1. The version of my Report Generation Toolkit is 1.1.2.
    Kind regards, Roman

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

  • 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

  • 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

  • Problems in using Application Builder to Build a exe file with Report generation Toolkit

    Hello,
    It's my first time to build exe. But I have Problem  when the VI have Report Generation toolkit VI.
    It's no problem in VI Format , But It can't work when I build as EXE format
    Can Anyone help me, and state step clearly in how to  solve the problems?
    Thank you!!

    If the code works OK in the development system but not in an executable there are a few things you can check. The two most likely causes are:
    There is an error occuring that your code isn't reporting.
    There is a file path that under the executable isn't valid.
    First make sure that all the error clusters are daisy-chained together in the subVI that you wrote to create and populate the excel file. Next make sure that the end of that chain goes to an indicator on the VI's front panel.
    Second, make sure there are indicators on other key parameters like the path the file is trying to write to.
    Third, temporarily modify the VI properties of that excel IO VI to open it's front panel when called, and rebuild your application. The next time you run the application the front panel will open when you try to write to the excel file and you should be able to see what is happening.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

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

  • 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 1.1.2 doesn't show up on the panel

    I installed Report Generation Toolkit 1.1.2 together with the Labview 8.5. But when I looked into the function panel, it didn't show up. No Labview has been ever installed on this machine. However when I went to control panel "Programs and Features"-> National Instrument, it did show the "Report Generation Toolkit for Microsoft Office 1.1.2" there. So I guess it did install it, but how can I add them into the function panel. Btw, my system is Vista.

    Hi lshi,
    Glad to hear that reinstalling the Report Generation Toolkit resolved
    the problem.  To answer your question, the installer prompts for an
    installation directory to allow users with multiple versions of LabVIEW
    to select a version other than the latest.
    Peter K.
    National Instruments

  • 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

  • Malfunctio​n in generating word report out of an app (using the report generation toolkit)

    I placed in my program some features that generate a word report with some graphics and text using the report generation toolkit. When I'm in the developing system everything works. But the point is that I have to create an exe for a user and in testing this the report is not generated (and no error msg occurs). Does anyone handeled this problem already and could give me some hints? Thx.

    Hi muchalla,
    the report generation toolkit for MS office depends on the version of MS Office (not the OS). You must generate your application for the version of MS Office or use some dynamic technic.
    The different versions of the llbs you need are on the CD in a subfolder called compability.
    Here I have asked if some ideas to do this will work. Until now I haven't got the time to verify it by myself.
    You will find here more information about using the report toolkit with applications.
    Waldemar
    Waldemar
    Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
    Don't forget to give Kudos to good answers and/or questions

  • How can I create a Report with the Report Generation Toolkit?

    Hi,
    I have installed Labview Report Gerneration Tool for Microsoft Office Version 1.1 and now I want to use MS Office Report Express VI but it need the VI "Dflt Data Dir.vi". I don't have this on my computer, why? Where can I get this VI? Can somebody help me?
    thanks Labprog

    Hello Labprog
    This VI should be located in the file.llb in the folder
    ..\vi.lib\utility. Thus, it is not part of the report generation
    toolkit but of LabVIEW. I am not sure why you are missing that file on
    your PC, maybe you just did not find it because it is hidden in a LLB.
    Maybe this LLB is not part of your LabVIEW package (Base, FDS, PDS).
    Anyway, I'll attatch that little VI, hoping that this is the only one missing.
    Ingo Schumacher
    Systems Engineer Sound&VibrationNational Instruments Germany
    Attachments:
    Dflt Data Dir.vi ‏11 KB

  • Does the Report Generation Toolkit need Office?

    Quick question: Does the Report Generation Toolkit (V1.1.3 for LV 8.6) need Microsoft Office installed in order to create Word documents?
    I have a need to create reports, preferably in Word format, but the target machine may only have the Word reader installed, not Office.
    Thoric (CLA, CLED, CTD and LabVIEW Champion)
    Solved!
    Go to Solution.

    Yes, you need office.
    Regards,
    André
    Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

  • Does the Report Generation Toolkit support Office 2007?

    With the hot-out-of-the-oven Office 2007, Microsoft has done a complete overhaul of the Office environment that we all have spent many years learning to perfection (well.. almost). Lucky those who got a head start as part of the Office Beta program.
    Well, NI claims that the current version of the LabVIEW Report Generation Toolkit supports "Microsoft Office 2000 (Word, Excel, and Graph) or later" and therefore literally also the new Office 2007.
    I doubt that the ActiveX API has remained unchanged when developing Office 2007, so let's use this thread to uncover the experience you have with calling Office 2007 applications using the LabVIEW Report Generation Toolkit.
    Anyone???
    - Philip Courtois, Thinkbot Solutions

    We are currently working on a maintenance release for the Report Generation Toolkit to support Office 2007.  You can install the current toolkit with Office 2007, but you will have some problems.  If you copy the four LLBs from the Compatibility\Office 2003\vi.lib\addons\_office folder on your Report Generation Toolkit CD to the corresponding vi.lib\addons\_office location in your LabVIEW folder after installing the toolkit, things will work for the most part.  But you won't have 100% compatibility until the maintenance release is done.
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

Maybe you are looking for

  • HELP: I need to link a PDF within PDF and be able to open and return to original PDF

    I have a master PDF and have attached 7 supplemental PDF documents. I created "click here" icons and used the steps below so that the linked document would open. The problem is, once I open the supplemental PDF, it closes the original master. I would

  • New order type for a purchase order similar tu UB.

    Hi, I would like to know if it is possible to create a new order type for a purchase order. This new order type should work as a UB order type but "plant" and "storage location" should be indicated by default and shouldn't be changed. How should I pr

  • Register xml schema in Oracle 9i error

    I got following ORA error when register xml schema in Oracle 9i. ORA-30931: Element 'seq' cannot contain mixed text ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0 ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 26 ORA-06512: at line 754 There is no mixed in

  • HT1390 Report problem with movie rental

    I rented the movie "Hunger Games". After the download had completely finished I wanted to watch the movie in iTunes and had trouble, the sound was on and off, the picture sometimes blurry and interrupted. How can I report a problem in movie rentals?

  • Nokia C6-00 : 'Edit label' option is missing

    Can anyone tell how to edit a label in a contact's details. If there is a label called Mobile, how can I change to Mobile (my place) ?. This option is present in my Nokia N79 and Nokia 5320 expressmusic.