MS Office Toolkit

I am trying the toolkit out for the first time to get some data out of an excel spreadsheet.  It appears that the toolkit only supports creating files, not opening/reading existing files.  All the installed vi's on the pallette are under Report Generation.  I was looking for the "Open Excel File" type vi and it is not there.  Is this right?  I was able to look thru the lower level vi's and figure out how to open files, but it appears this functionality is not supported at the top level?  Unless I'm missing something, it looks to me like the toolkit only has half the functionality it should.
Bill F

Hey Bill,
Here is a sub vi I wrote that opens an excel file then extracts data from named cells in excel and writes it to a spreadsheet.  I had to search the forums for a little bit before I figured out how to do it myself.
The reason for the error case is because sometimes excel would not open for every file I was looking in for data.  I was getting data from 50+ excel files and random files would not get opened giving me bad data.  I guess it is a known problem that excel sometimes takes too long to open and will generate an error.
Bryan
Attachments:
Open Excel.PNG ‏26 KB

Similar Messages

  • Reading Values from Listbox and data source into MS Office Toolkit

    Hi,
    Been trying to get this to work but making no progress and my lack of experience on labview is becoming a hinderence.
    Does anyone know how I can read the values from the listbox example attached into MS Office Toolkit for Excel?
    The values from the listbox need to be compared to mulitple values from a strain data source.
    Cheers,
    Mike.
    Attachments:
    Capture.PNG ‏62 KB

    Hi,
    Ok in the attached vi I want value from the listbox "0kg through to 10kg" to be put into the excel table in the report generation toolkit along side data from the convert strain gauge reading.
    Cheers,
    Mick.
    Attachments:
    Strain Gauge Edit2.vi ‏112 KB

  • Creating installer with office toolkit 1.1.1 and labview 8

    HI All,
    I am developing a large application with labview 8 and office toolkit 1.1.1 installed.
    We need to make an installer to distribute our application to all of
    our contractors (hundreds of them) for direct them in methods of
    procedure during construction, conformance reporting, inspection and
    test plan reports and finally uploading data gathered during
    installation and testing to our network assets database.
    I have successfully programmed the code in Labview 8 and have the
    report generation functioning satisfactorialy, but when i create the
    executable, i get the following message when trying to generate a
    report:
    Error 7 occurred at Open VI Reference in New Report.vi->PrintWordReport.vi->Compile MOP.vi->COAT_Top Level.vi
    Possible reason(s):
    LabVIEW:  File not found. The file might have been moved or
    deleted, or the file path might be incorrectly formatted for the
    operating system. For example, use \ as path separators on Windows, :
    on Mac OS, and / on Linux.
    NI-488:  Non-existent board.
    VI Path: C:\Documents and Settings\John\My Documents\NATIONAL
    INSTRUMENTS\COAT\builds\COATAppBuildScript2\My
    Application\Application.exe\Word_Open.vi
    Built Application or Shared Library (DLL): Make sure all dynamically loaded VIs were properly inc
    Fair enough..... i consulted the toolkit manual which said that i need
    to include the following llb's in the source file in the builder: "
    _exclsub.llb and _wordsub.llb.
    When i include these llb's in the top level folder in the project
    window and try to build the exe again, i get the following"The file
    already exists in the destination.
    C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\addons\_office\_wordsub.llb
    BUT my destination directory is in the "my documents" folder, not in the above path!!!
    What is going on?????
    Problems part II ---
    in the toolkit, there are different excel and word llb's for each different version of office.
    This application has to distribute to many different computers, each with different versions of office.
    How do i include the correct llb's for the correct version of office for every PC?
    Any help would be greatly appreciated.......
    regards
    John

    Hello John,
    I. How are you adding the support files? Are you adding them when creating the executable in the source files configuration page of the build script, and if so are you marking them as dynamic VIs?
    II. That’s a tough one. Since the ActiveX structure changes from one version of office to the next it would be difficult to create one executable that will work on all versions. Currently you need to have the same version on your dev machine as you do your target. Sometimes you can get away with not having the exact same version if you are only doing very generic things and the ActiveX structure hasn’t changed for those things between versions, but that is a little risky. It may be a good idea to build a couple of versions of your VI for the two or three most recent versions of Office
    Regards,
    Chris J
    Why Won’t My LabVIEW Built Executable Work With Microsoft Office 97 if I Developed the Code on a System with Microsoft Office 2000?
    http://digital.ni.com/public.nsf/websearch/D4D32D45EAD5830186256BD800506A41?OpenDocument
    Error 2146959355 When Running Exe on Machine With Different Version of Office
    http://digital.ni.com/public.nsf/websearch/83211E3A088D0C3786256DB700621FE8?OpenDocument
    Error 7 WhenBuilding Applications and DLLs That Use the LabVIEW Report Generation Toolkit
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/86256a47004e16d186256a84004cb883?O...

  • MS Office Toolkit- spreadsheet appears on top of VI

    I have a vi that opens, writes to, and closes an Excel .xlsx file. When I operate this from my desk computer, I see the spreadsheet open and close BEHIND the calling vi. No problem. On another computer, the spreadsheet opens IN FRONT of the calling VI and obscures my vi's popup message, and the spreadsheet remains, effectively locking vi execution unless I move it aside. Both computers have the same Labview 2011 SP1 and same MS Office and same MS Office Toolkit. The latter behavior is the problem one. Why does it behave differently?

    I think I understand my problem. The difference is the monitors. Where the problem does NOT exist, I have a larger monitor with higher res, and I can see the spreadsheet popup behind it. On the "problem" computer, it has a smaller, low res monitor and the VI occupies the entire screen. Must be the spreadsheet is FORCED to appear in front of the VI on that monitor. In any event, I can fix the problem by using Excel Bring to Front and setting window state to Minimized. I just thought it curious that the fix was needed on one computer/monitor and not the other.

  • Can't install ms office toolkit 1.1.1 to LV8.6

    anyone had had a problem installing the MS office toolkit 1.1.1 to LV ver8.6? I did unistalled 8.5 where the toolkit worked fine. I installed to another directory and seems to install without any problems, but when I run vi's where I used the toolkit they don't work well (I get errors realted to the tool kit subVI's). very strange stuff. thanks for any help.
    Attachments:
    Error 1301 MS office toolkit.doc ‏30 KB

    Hi Otman,
    You can install an evaluation version of the newest version of the Report Generation Toolkit for Microsoft Office, which is actually now version 1.1.3 here. Download and run the .exe, and then you can activate the product using your activation information.
    Regards,
    Stephen S.
    National Instruments
    Applications Engineering

  • Smtp email (MS office toolkit) can't open attachments

    I'm using the SMTP Email send file.vi to send a Word.doc file as an attachment. The .doc file is the result of the MS office report.vi opening a template, filling the bookmarks, then saving the file as a .doc.
    The .doc is then opened with the New report.vi, printed (print report.vi), then disposed (disposed report.vi). The .doc is then attached to an email using SMTP email send file.vi.
    The email(s) are arriving without problem and the attachment is visible. If, however, the attachment is double clicked, it will not open. The error message indicates that there may be either path or security problems. There is not, I'm sure of it.
    Additionally, I tried saving the attachment "SAVE AS" to a local drive and then opening it. The "save as" worked alright, but when opeing the file I got the same errors.
    Oddly enough, if I navigated to the location where the MS office report.vi saved the .doc file and then opened the file, everything worked as expected. The file opened and the bookmarks were filled in as expected.
    It seems to me that Outlook (exchange server) is doing something to the file (freakin Microsoft). I can't imagine, however, that I'm the first to attach a file to an email using the MS office toolkit.
    Somebody please shed some light on this. It's driving me nuts.
    thanks,
    todd

    Hi Ma,
    Here's the "Emailing_Reports.zip" including the VI for LabVIEW 7.0.
    Please notice that the option of setting the "binary?" connector to TRUE, is specific to the "SMTP Email Send File.vi" and not just to this example.
    Good luck!
    - Philip Courtois, Thinkbot Solutions
    Attachments:
    Emailing_Reports.zip ‏91 KB

  • Microsoft office toolkit erreur transcription date

    Bonjour,
    Je génére des tableaux de données depuis un fichier txt vers un fichier xls en utitlisant labview et le microsoft office toolkit. mais j'ai un pb pour le transfert des dates. Le format date est JJ/MM/AAAA dans le fichier txt. Lorsque le transfert du txt vers excel se fait s'il y a un changement de mois le format date devient MM/JJ/AAAA et je ne comprends pas pourquoi.
    Merci
    Pièces jointes :
    Labview erreur date.JPG ‏216 KB

    bonjour as-tu vu
    http://forums.ni.com/t5/Discussions-au-sujet-de-NI/inversion-jour-mois-dans-excel/m-p/2512108/highli...
    Tu devrais essayer en string au format iso %Y-%m-%d %H:%M:%S
    Luc Desruelle | Voir mon profil | LabVIEW Code & blog
    Co-auteur livre LabVIEW : Programmation et applications
    CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
    CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW

  • Control checkbox form field in word with report generation toolkit for Microsoft office

    Hi all,
    Happy New Year!
    I insert in the word template the check box form field. It has a bookmark name "Check1".
    Now I'm trying to checked or unchecked this field using the report generation toolkit for Microsoft office and I couldn't. If anyone now how to do it? I'm using LabView 8.0
    Thanks in advance,
    Boris
    Solved!
    Go to Solution.

    Boris,
    The Microsoft Office Toolkit does not have support for checking/unchecking check box forum field. You would have to research the activex functionality that enables this to be checked or unchecked and then do the activex calls yourself. I did hear of one csutomer who used a special font to write a blank box or a checkbox into a word document and changed it that way as well.
    Maybe http://www.ozgrid.com/forum/showthread.php?t=53715 gives a hint to an activex reference
    Rob K
    Measurements Mechanical Engineer (C-Series, USB X-Series)
    National Instruments
    CompactRIO Developers Guide
    CompactRIO Out of the Box Video

  • MS Office (Excel) Toolkit - trouble formatting cells

    I have the MS Office toolkit 1.1 and LabVIEW 7.0. I am using 'Excel easy table' to write arrays of strings (number strings and titles, etc.) to a spreadsheet but I also want to control the number of decimal places and the number format.
    I want to use 'Custom ##0.0E+0' number format (engineering notation) and I want to have 3 or 4 decimal places. Currently, the format of the number written into Excel changes based on whether I converted from a number to an engineering string (engineering notation is not preserved in Excel) or if the string in the array is read straight from my GPIB query. I want to be able to control these things within LabVIEW. Any suggestions are appreciated.
    Sara

    Hi Sara,
    The easiest thing to do would be for you to create your new report based off a template Excel file. I have attached a sample VI and a sample Excel template that show how to do this. If you know which way you want individual columns to be formatted, this is the easiest solution. If, however, you might have different formatting that needs to be assigned dynamically, you will have to use the more advanced Excel VIs, like the "Excel Set Cell Format.vi", located in the Excel Format subpalette. There is an example that ships with the Report Generation Toolkit that uses this VI to set the colors of certain cells in the spreadsheet...the example is located at examples\office\Excel Examples.llb\Conditionally Formatted Spreadshee
    t.vi.
    I hope these suggestions help. Good luck,
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman
    Attachments:
    formatted_template.xlt ‏14 KB
    Report_With_Template.vi ‏34 KB

  • Report Generation Toolkit

    I get the error 7 from runtime labview applic. that use the report generation toolkit. This work fine in the develoment environment. This question i did before and was solved.Right now i reisntall the software and i forgot the solution.But was somthing relate with the funcion Excel Find aplication directory.vi I change the path, but i don not remember well. The Microsoft development tool kit is ver 1.0.1. Thank in advance

    Hi Josorio
    Report Generation Toolkit 1.0.1:
    It's important to include a dynamic VI when building an application which uses the Report Generation Toolkit. Please check this for more informations:
    http://digital.ni.com/public.nsf/websearch/86256A47004E16D186256A84004CB883?OpenDocument
    In Report Generation Toolkit 1.0 you got an Error 7 when running executable with Office Toolkit with the "Support File Directory" in App Builder as something other than "/data". The /data directory is hardcoded in the "Excel Find Application Directory.vi" and in the "Word Find Application Directory.vi". If necessary, the string constant in these VIs can be changed so that they reference a directory other than /data.
    Regards,
    Luca
    Regards,
    Luca

  • Report Generation Toolkit and Applicatio​n Builder

    I am going insane trying to work this out.
    I am trying to build an EXE program using Application Builder. The program uses the Office Report Generation Toolkit.
    I have tried including the dynamic VIs into the project, both from the Development machine and from the CD. I still have the same problem : the application does not start Excel. It is like the commands go into a black hole. There isn't even an error message.
    I have attached my report VI for you to peruse. Any help is appreciated.
    Brian Rose
    Solved!
    Go to Solution.
    Attachments:
    TestReport.vi ‏122 KB

    Yes, Labview 8.2
    Office Toolkit = 1.1.1
    I have tried many combinations of what files are included, from just the top level VI, to every VI in the heirarchy tree (a major pain). I am now trying to rebuild the project from scratch and see if that does anything.
    Brian Rose

  • Report generation toolkit with excel 97 Graphing issue

    I am trying to set-up mu data output to use the report generation Vis. However I am running into a problem when trying to update 2 graphs on the same sheet in Excel.
    My set-up is:
    Windows XP
    Office 97
    LabVIEW 7.1.1 with the Office toolkit installed
    I noticed that I can write to the first Graph and update it without issues, but once I try to update the second I get error -41105 stating that MSGraph is not installed.
    I did notice that if I set a break point between the Excel Quit Graph.vi and Excel Update Graph.vi if I click the mouse within excel in removes the highlight border from the first graph, the I continue and it works fine. For some reason LabVIEW is not releasing that Graph to be able to select another.
    I tried to write data to a cell after quiting the graph and then selecting the second graph but that is not working either although it does work manually.
    Next I may try a Macro but I would rather not have to do that.
    Any suggestions?
    Jeff
    Jeff D.
    OS: Win 7 Ultimate
    LabVIEW Version: 2011,2010,2009 installed
    Certified LabVIEW Architect

    Well after some debugging I found it. Apparently for Excel 97 only there is a problem that when you qiut MSGraph it may not save properly so the VI had the Quit Property removed.
    I have added it into my code and it seems to work and will see how well it does and if I run into any problems.
    Jeff D.
    OS: Win 7 Ultimate
    LabVIEW Version: 2011,2010,2009 installed
    Certified LabVIEW Architect

  • AppV5 Excel/Office ProPlus 2013 Click to Run Sequencing (and include some native Addins)

    Hello,
    We need two native Excel 2013 Addins: PowerPivot and PowerView. Since Office 2010 is installed locally on all client machines I would like to virtualize Excel 2013 (Click to Run) with these two addins. Licensing is no issue because an
    Office 365 subscription will be purchased.
    So, I have successfully sequenced Excel 2013 with AppV 5.0 SP1 via the Office Deployment Tool. It all seems too easy:
    First download sources (setup.exe /download configuration.xml)
    Second configure sources (setup.exe <xml file>)
    Last create the AppV package (setup.exe /packager <xml> <path to save .appv package>)
    My Configuration.xml file looks like this:
    <Configuration>
    <Add SourcePath="\\serverr\share" OfficeClientEdition="32" >
    <Product ID="ExcelRetail">
    <Language ID="en-us" />
    </Product>
    </Add>
    <Display Level="None" AcceptEULA="TRUE" />
    <Logging Name="Office2013Setup.txt" Path="%temp%" />
    <Property Name="AUTOACTIVATE" Value="1" />
    </Configuration>
    But I end up with an Excel 2013 AppV package that:
    Doesn’t include the addins (no wonder because I didn’t sequenced it myself).
    All the 'first run wizards' popup at launch (Default File Type question & Welcome to your new Office). Normally I disable these with OCT for physical installations, or configure them while sequencing.
    Is there a way to disable the first run wizards in the “setup.exe /configure” step? And can I add Excel Addins during package creation? Or need I script this within the DeploymentConfig.xml/UserConfig.xml with a .reg import for example?
    Thanks,
    Ben

    Hello,
    We need two native Excel 2013 Addins: PowerPivot and PowerView. Since Office 2010 is installed locally on all client machines I would like to virtualize Excel 2013 (Click to Run) with these two addins. Licensing is no issue because an
    Office 365 subscription will be purchased.
    So, I have successfully sequenced Excel 2013 with AppV 5.0 SP1 via the Office Deployment Tool. It all seems too easy:
    First download sources (setup.exe /download configuration.xml)
    Second configure sources (setup.exe <xml file>)
    Last create the AppV package (setup.exe /packager <xml> <path to save .appv package>)
    My Configuration.xml file looks like this:
    <Configuration>
    <Add SourcePath="\\serverr\share" OfficeClientEdition="32" >
    <Product ID="ExcelRetail">
    <Language ID="en-us" />
    </Product>
    </Add>
    <Display Level="None" AcceptEULA="TRUE" />
    <Logging Name="Office2013Setup.txt" Path="%temp%" />
    <Property Name="AUTOACTIVATE" Value="1" />
    </Configuration>
    But I end up with an Excel 2013 AppV package that:
    Doesn’t include the addins (no wonder because I didn’t sequenced it myself).
    All the 'first run wizards' popup at launch (Default File Type question & Welcome to your new Office). Normally I disable these with OCT for physical installations, or configure them while sequencing.
    Is there a way to disable the first run wizards in the “setup.exe /configure” step? And can I add Excel Addins during package creation? Or need I script this within the DeploymentConfig.xml/UserConfig.xml with a .reg import for example?
    Thanks,
    Ben
    You said you used the Office Toolkit? In this you can set Disable Opt-in Wizard on first run.
    Was this used when installing on the sequencing machine?
    Alternatively you could attempt to launch excel during the sequencing phase and go through those menu's to ensure they don't launch on first launch of the virtual Excel. I believe that shouldn't be a problem since.
    For the Add-in's, it seems like you know they weren't included or connected in any way, that's likely the issue with those.
    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
    rorymon.com Twitter: @Rorymon

  • How to create report on excel without excel toolkit??

    Can anyone please tell me how to create an excel based report (much like what an excel toolkit produces) without having the luxury of
    an additional Microsoft Office toolkit/???
    thanks
    Now on LabVIEW 10.0 on Win7

    okey... simple question... i got the NI OFFICE toolkit, and i want to save all my DAQ data on an excel sheet and plot the graph for it....(create a report)
    my sampling speed it not much, 1 sample/sec. i am using the MS Office Report.vi to save the report to a file. however, i observe that if i add the MS Office Report.vi in while loop,
    the program keeps on asking for a file name every iteration unlike the Save to Measurement file.vi (where it asks only once and then keeps on adding data to the next file unless 
    any other logic is applied). also, it only saves the first 3 rows of data.
    how do i make the code so that the excel file saves the entire data and the graph plots a summary kind of plot of the data i have from the DAQ.
    Thanks in advance.
    Now on LabVIEW 10.0 on Win7

  • Report generation VIs in Labview 6.1

    Hello,
    I am havinf problems with using Labview 6.1 VIs for report generations. The VIs provided by Labview are not executable! It seems as if they had internal errors, non fixed errors. Moreover, I am not able to open the diagram because it is password protected. Does someone know if there is any patch to fix this or the reason why these VIs don't work?
    Thanks a lot!
    Regards,
    María

    Hello Maria,
    are you using the report Generation Toolkit for MS Office or the standard vis that LabVIEW provides for report generation?
    If you use the Office toolkit, this may help:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/c8888a9a74e75c4786256cda00694a1e?OpenDocument
    If not, this may also help:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/9acb175f6de483ae86256b2200776b8b?OpenDocument
    In any case, WHAT I WOULD TRY FIRST is to do a Mass Compile of the folder where the report vis are located.
    Here you can see what this does and how to perform it:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/654877e62a97b72986256c95006f9b24?OpenDocument
    One last question...are you having trouble only
    with executables or also during development?
    Regards,
    JorgeM.

Maybe you are looking for