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.

Similar Messages

  • Where can i download the trial version of the Labview 2013 64bit Report Generator Toolkit for Microsoft Office?

    Hi all,
    I am having trouble locating a LabVIEW Toolkit.  Could somebody please send me a link to somewhere where I can download the eval version of the Report Generator Toolkit for Microsoft Office for LabVIEW 2013 64bit.?
    Thank you in advance,
    Bob

    Yes here is the 2013 version.
    http://download.ni.com/evaluation/labview/ekit/oth​er/downloader/2013RGT_downloader.exe
    And here is the 2014 version.
    http://ftp.ni.com/evaluation/labview/ekit/other/do​wnloader/2014RGT_downloader.exe
    I believe both are for 32 bit LabVIEW, which works in both 32 bit and 64 bit Windows.  Honestly until all toolkits support 64 bit Windows, I still don't see much of a reason to go with 64 bit LabVIEW.  The support is just better with 32 bit.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • 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

  • 2010 Report Generator Toolkit Installation

    I've installed 64-bit LabVIEW 2010 into C:\program files\National Instruments\LabVIEW 2010 and the 32-bit version into C:\program files(x86)\National Instruments\LabVIEW 2010.  My PC is 64-bit and runs Windows 7.  When loading a program written in LabVIEW 8,5, both versions (32 and 64-bit) don't load quite a few libraries and VIs such as "NI_ReportGenerationToolkit.lvlib", "Set Current Font.vi", "Excel Set Cell Font", etc.  I can search for these files in Windows and select them when I load my main VI, but I still end up with broken arrows in the code.
    I also don't see the Excel-specific or Word-specific functions in the Report Generation palette.
    I've uninstalled the Report Generation toolkit and re-installed it from the DVD (per another thread) but that didn't work. 
    Could someone explain where the libraries are supposed to be for both 32-bit and 64-bit?
    Thanks in advance...

    Hi SJT,
    I would suggest trying two things. The first is to ensure that you are restarting LabVIEW and your computer after you have installed the toolkit. If the toolkit still does not appear on your pallets I would then suggest downloading the Report Generation Toolkit from the Service Resource Center and using that media to run a Repair on the toolkit.
    You can also double check the library is in the correct place by looking in your Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\addons\_office directory. 
    <Brian A | Applications Engineering | National Instruments> 

  • Save NI report generator files with new names

    I was trying to save labview library files under new names so that I could adapt the code but the 'Save As' option is greyed out. In certain cases, when I try to copy and paste the code, I get broken wires and cannot get the VI's to work.
    I have been using the report generator toolkit which is quite limited. I was trying to delete a row from an spreasheet but there is no function to do this. So, one workaround that was suggested to me was to use the 'Excel Insert Cells' VI and change the code to instruct it to 'clear' cells rather than 'insert' them. This works, but I wanted to save a copy of the amended file under a different name so that it was independent of the installed library files but I can't seem to do this. I tried to copy out the code but got broken wires even though I have been able to do this in other instances.
    Any suggestions?
    Thanks,
    Will

    Hi Will,
    I had the same problem with a project and found the following workaround:
    To ensure the original function of any library VI, it's not recommended to just change the VI to do something else.
    Therefore I expanded the VI to do both, the original functionality and the special function I needed.
    I made an extra Input to the VI, which is a boolean Input.
    With that extra optional Input I can now choose the function I want to do.
    I made the "False" case to be default. This case works like the original function.
    The "True" case is built to do my special function.
    This workaround is quite easy and not dangerous. For all projects, which would use the function in their normal use case it's working just as if the file was unchanged.
    And for projects using special functionality I can add a "True" constant to my VI Input and the function works as I want..
    Hope this workaround helps to fix your problem!
    Kind regards
    adigator

  • 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

  • Can I align the orientatio​n of axis labels in a graph generated with the report generation toolkit (Word)?

    I was wondering how to align the axis labels, i.e. 90 degree or such when creating a graph with the report generation toolkit in word.
    I can do it after the document is created through Format axis title -> alignment but is there a way out of LabVIEW?
    I'd especially like to rotate the y-axis label by 90 degrees.
    Thanks a lot,
    Juergen

    I think he means he can modify it by hand after the report has been generated... But what I want to do is generate the word graph out of labview already with the rotated axis label...
    After I posted this I found out that we can do this with a macro and use it from labview, but unfortunately I don't know VB, or VBA...
    Like this:

  • Changing the Size of generated graph in excel report generation toolkit

    Hi, i am trying to build a report generation vi for my Structural health monitoring system in which i need to export 3 graphs in to an excel report. The idea is to have the report on a single page, but when i paste them along with the ceiling and pillar deviation percentages, the report just exceeds the page limit. I wanted to know whether one can change the size of the graphs in excel? One can do it in word(tried that), but i dont want to use the bookmark option as it intend to put this up as a webservice in the next step. I am using LabVIEW 2009 Thanks.
    LabVIEW 8.2,8.6,2009...still learning
    Attachments:
    Report Generation SHM.vi ‏30 KB

    Hi,
    I haven't tried this myself, but looking through the report generation toolkit the "Excel format image VI" (in the Excel specific tab of the Report Genertaion window) looks to be the one you are after. The help entry for the VI says to: "Use this VI to format any type of image in a worksheet, including front panel images, images from a file, and graphs"
    Hopefully this will help.
    -CC 
    "If anyone needs me, I'll be in the Angry Dome!"

  • 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

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

  • 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

Maybe you are looking for