Path to save problem in report generation toolkit

Hi,
I am newbie in LabVIEW. I am using MS Office Report.VI from Report Generation Toolkit, and I want to let the user to choose the save location for the report. I tried to wire path control to "Path to Save Report" input on MS Office Report.VI . But It doesn't work, It seems like the destination choosen from path is overlapping with the base file destination on "Configure Save to file options".
How do resolve this issue??
Thanks

You are using an express vi hence you are limited in options. Express vis are a good starting point but if you need to customise , you may need to use individual vis.
Try searching for 'office' in example finder (Help >> Find Examples), you will find a lot of them, chose one that suits you.
Hope this helps.
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Similar Messages

  • 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

  • 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

  • Problem with report generation toolkit

    I am using labview 2011.
    When I right clicked on block diagram I can see reprt generation toolkit. But when I am trying to use it to save a word file I faced a error code-41007.Please help me..........
    Thank you in advance........

    Here's the download for the LabVIEW 2011 version of the Report Generation Toolkit:http://www.ni.com/download/labview-report-generati​on-toolkit-for-microsoft-office-2011/2572/en/
    But you keep saying you installed and uninstalled the RGT.  What version were you installing and uninstalling?  Is it currently installed?
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Problem with report generation toolkit when installed new office 2010

    Dear all, I had  LabView 8.6.1 and report generation toolkit for MSoffice 2003 perfectly working in my laptop.
    Now I have added MSoffice 2010 and report generation toolkit does not work anymore since it is linked to new office.
    How can I inform Labview to link report generation toolkit to the old  MSoffice 2003?
    regards
    Max

    The Report Generation Toolkit is ActiveX based.  When you install the newest version of Office it registers the ActiveX server for that software, which the toolkit adapts to and uses.
    Uninstalling Office 2010 would solve the issue, otherwise you will need to look at unregistering the 2010 component of Office ActiveX - but I'm not sure if that's possible.
    Regards,
    Peter D

  • REPORT GENERATION TOOLKIT AND EXCEL

    i have a problem with report generation toolkit and excel
    the problem is:
    i must read & write from a excel worksheet when this is open but when i using the report generation the worksheet is open another time
    have some solution for this problem?
    sorry for my english

    You need to close Exel when before your VI is running. Excel can not have two instances running at the same time.
    Joe

  • 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

  • Problem building applicatio​n using Report Generation Toolkit, LV 2011

    I'm using LabVIEW 2011 under Windows 7.
    I tried to use Application Builder to create an executable from a large body of code. One thing the application does is load VIs into a subpanel and run them.
    Application Builder created the executable and gave no error message. The built application ran except that it couldn't run any of the dynamic VIs.
    I finally succeeded in doing a screen grab on a transient dialog (about 1/10 sec. appearance). The dialog showed an attempt to load <vilib>:\Utility\NIReport.llb\NI_report.lvclass.
    In one dynamic VI I commented out the call to the only VI that uses the Report Generation Toolkit (called only from dynamic VIs, all of which call it). Sure enough, when I built the application with that change and ran it, the dynamic VI that didn't invoke the Report Generation Toolkit did successfully load into the subpanel and run.
    So, trying to prove to myself that that was the only problem, I wrote a VI that does nothing but load a VI into a subpanel and run it. User can choose one of two VIs: one that doesn't call the Report Generation Toolkit (or do much of anything), and one that does. Both VIs run fine standalone.
    The not-much-of-anything VI loaded and ran in the subpanel. The other VI didn't--the same dialog, mentioned above, popped up for 1/10 second or less. Screen grab is attached.
    When I included LVClass and NIReport.llb folders in the project (from vi.lib\Utility: Snapshot folders), and "Always Included" those folders (per a suggestion on this forum from a few years ago), the result was the same. The result was also the same when I included either one of those folders but not the other. Likewise it doesn't matter whether I add the dynamic VIs as "Always Included" or not.
    Another piece of information that may be pertinent: when adding the NIReport.llb folder, I got a message that it was impossible to add a certain VI that's part of some report-type class, because a VI of that name already existed in the project. Screenshot of that dialog is also attached.
    VIs and project file are also attached along with the two screenshots. I hardcoded VI paths, so put everything into C:\Testing if you want to see what the code does--or hack as desired, etc.
    I will be deeply grateful for any help! And I apologize in advance if there's already some exact or close-enough solution posted--but I doubt there is. I looked around.
    Thanks very much,
    mws
    Attachments:
    Test-App-Build.zip ‏336 KB

    Hi again,
    If you extract all files in the original zip attachment to a folder called C:\Testing on a Windows 7 machine running LV 2011, and then use the build script within the project file to build the application, you can run the application and see what happens. You can also play around with the build parameters, rebuild, run, and see what happens then. You can also open my VIs and see what I'm doing.
    The application lets you pick one of two dynamic VIs to run in a subpanel. One VI contains calls both to Report Generation VIs and some functions from the Advanced File Functions palette. The other VI does not.
    When you pick the first VI to load and run (the one with the Report Generation and Advanced File Functions calls), it loads into the subpanel but is not executable.
    When you pick the second VI to load and run, it does load into the subpanel and execute. So there's nothing wrong with the way I load and run a VI in the subpanel.
    In the development environment, the whole thing runs with no problems.
    Evidently the built application has problems resolving paths of something called by Report Generation VIs and by the Advanced File Functions I use.
    I've done a lot of experimenting and no luck. I've looked in forum archives, etc. etc., for possible solutions. I'm hoping there's some simple solution I've missed.
    Thanks very much for any help!

  • Report generation toolkit problem

    hello everyone,
    i am using Export waveform to Spreadsheet.vi for getting data into excel. i have downloaded  and install the Report Generation toolkit 1.13 for make it working but still it seems not working 
    i am using labview8.6 on windows xp with Microsoft Excel 2003 .
    i have tried the same vi on an other  computer with same configuration and it works there, but not on my PC, i want to ask is there any thing wrong with my version and the Report Generation toolkit? or i am installing it wrong? or is there any specific folder or path i have to mention during installation of toolkit? if yes then how could i uninstall the existing toolkit because i couldnt find the installed toolkit path or location on my PC?
    thanks
    looking forward ... 

    Hi Hussain,
    Are you still having these problems.
    Can you use other functions in the toolkit or is it just that one.
    Do you have other versions of labview than 8.6 intalled on your computer ?
    /Christine

  • Office Report Generation Toolkit 1.0.1 and MS Office 2000 problem

    Hello.
    I'm tring to make a repot in word using a template..everything works just fine when in development..but when i make the executable the problem arises.
    I get error code 7  (Cannot open vi reference) in NewReport.vi.. FYI i'm running the aplication in the same machine i'm developing.
    I'm sure everything else is ok..- changed paths to work in executable, template in correct folder...i'm adding the necesary support llb to the executable(Win200), etc - ..i tried reinstaling office and the report generation toolkit but i still have the same problem...
    How can i solve this?....
    Thanks in advance for all yur help.

    Well..that was a very good answer to my question...and it solved my problem. Thank you.
    I thought that by adding just the llb as support files would be enogh..but now i see this is not correct..thanks again.

  • Report Generation Toolkit Print HTML Problem

    Hi,
    i have a problem printing a html Page at a Costumers PC with the Report Generation Toolkit.
    I use LV 2012 and the Report Generation Toolkit in 32Bit Mode.
    The Target is a Win7 64Bit Machine with IE10 of our Customer with very strong security rules.
    Our Programm generates a HTML Repor which is saved without any problem.
    When i then try to print it with Print Report.vi it doesent work and i get error1 out of the SubVi NI_ReportGenerationCore.lvlibrint HTML Report using IE.vi.
    This Sub.vi simply cant open the HTML Page with the IE.
    I think its the costumers Security Rules that cause the Problem.
    I saw a very strange behavior of the IE.
    When i double click the .html file the IE gets opened and displays the file properly.
    When i then hit the reload button it also gets reloaded.
    When i click in the browsers adress bar and hit enter (Which normaly does a reload) i get an error "Adress Bar, Adresse, access denied".
    And i think that happens in the Sub.vi.
    I talked to some friends an they sad it could be that double clicking and reloding is done with the local user an the clicking and hitting enter reload is maybe the systemuser.
    So i asume that the Sub.vi is also using the systemuser.
    How can i determin which user is used to execute a vi?
    Can i influence the user?
    Has anybody a solution and seen this problem?
    Regards,
    westgate

    If I understand your situation correctly, you are able to use the LabVIEW Report Generation Toolkit to create an HTML report, which you save as an HTML file.  Can you open it in a browser and print it using the browser's Print button?  I've use LabVIEW to generate HTML reports, but have never tried to print the Reports in LabVIEW -- I've always used the "browser route", myself.

  • 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

  • Getting "Save File" permission message related to Report Generation Toolkit

    I started having this problem about a month ago.  It does not affect the operation of my project but is a minor nuisance, but a nuisance none the less.  I opened a couple of Excel Specific VIs.  I did not nor did I attempt to make any changes, I was just curious as to their content (truth is I wanted to see how the active X controls were being used).  Ever since then I get the attached messages when saving my project and have not been able to get rid of it.  When OK is pressed, a Save As dialog box appears (see attached) pointing to the NI directory which contains the Excel VIs for the Report Generation Toolkit.  I press cancel and am able to save my project VIs just fine, but I would like to get to the bottom of this problem.
    I would not think that simply opening a VI would cause this behavior.  I should also mention, it not only attempts to save the VIs I opened, but every RGT VI that is a part of my project, which is even stranger.  I have not attempted a reinstall.  I was hoping for something a little less drastic, and that won't prevent this from happening again, unless I can kill my curiousity that is. Is there a setting somewhere which I am missing?  Thanks in advance for your assistance.
    Reese
    Reese, (former CLAD, future CLD)
    Some people call me the Space Cowboy!
    Some call me the gangster of love.
    Some people call me MoReese!
    ...I'm right here baby, right here, right here, right here at home
    Attachments:
    Save Message.JPG ‏249 KB
    Save As Dialog box.JPG ‏305 KB

    It did not work.  In fact, it called out four bad VIs (see attached).  But I think this is probably normal behavior.  All the VIs in question are broken due to an unwired input on the bundle.  The bundle is the only thing in these VIs.  Could you please verify that this is the case.  It said the mass compile was complete and I am assuming that it did compile the rest of the VIs, correct?  Unfortunately I am still getting the same message.  Do you have any other ideas?  Anyone?  Thanks again for your assistance.
    Reese, (former CLAD, future CLD)
    Some people call me the Space Cowboy!
    Some call me the gangster of love.
    Some people call me MoReese!
    ...I'm right here baby, right here, right here, right here at home
    Attachments:
    Mass Compile Dialog.JPG ‏338 KB

  • Problem writing to excel file using report generation toolkit

    hello everyone, i have this report generation toolkit... and i want to output DAQmx Analog I/P data on to an excel sheet. the DAQmx is programmed to collect 
    data at 3samples/sec. however, when i see the excel file that Report Generation Toolkit generates, the time stamp is updated every second instead of every 0.33sec. 
    can anyone please help me?  i am using the MS Office Report Express VI. 
    Now on LabVIEW 10.0 on Win7

    @All, I got rid of the express VI, decided to work on the custom low level VIs instead. however, i have a new problem now... 
    I have a case statement wherein, the user selects if he wants to start generating a report. once the program enters tat loop, the program speed reduces! 
    can anyone please tell me why is it happening? i ahve attached the vi... also another question.. in this VI, i am capturing the unwanted data into the graph as I am indexin the graph input. how can i make a logic 
    that the graph captures the data only when I am switching the CREATE REPORT button (which is in the while loop). is there a way that I can append the data to the graph without creating a new graph every iteration? please let me know
    thanks
    Now on LabVIEW 10.0 on Win7
    Attachments:
    Untitled 7.vi ‏75 KB
    Untitled 7.JPG ‏99 KB

  • Report generation toolkit problem with office 2000 and office XP

    Hello, I am having a problem with running my vi after it is compiled with application builder. The dev machine is an XP box and the targer is windows 2000. I included _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi from the office 2000 section of the install cd (for the report toolkit) in the compile but did not include those files for XP. When I run the application on the target machine (2000), the reporting functions call Excel just fine and the program does not come up with any errors. The program however, is not loading the approprate template and inserting the approprate data. Did I leave some neccessary files out of the compile? Thanks in advance!
    Greg
    Gregory Osenbach, CLA
    Fluke

    Hi Acer,
    The recommended procedure in your case is to install Microsoft Office 2000 on the development machine and then reinstall the LabVIEW Report Generation Toolkit. When the toolkit is installed, it will check for the current version of Office and install the corresponding VIs to support it. The VIs include different ActiveX calls according to the version of Office. Therefore it is not enough to change the support manually without having the correct version of Office installed first.
    However, I would recommend that you just try to run your executable on a machine that has Office 2000 installed. The difference in the ActiveX API for Office XP and 2000 is not that significant, so your application might work perfectly on an Office 2000 machine. If you try to run the executable on a machine with Office 97 installed I'm willing to bet my right arm that you will experience errors.
    Good luck Acer!
    - Philip Courtois, Thinkbot Solutions

Maybe you are looking for