Report Generation Toolkit and Office XP and 2K

Hello Everybody
I am having few problems with running executable using Report Generation Toolkit on machine with Office 2000, which was compiled and build on machine with Office XP (toolkit also XP).
There are many errors which pops up, but the very first one is that the "New Report.vi" can not open the existing Excel book.
Is there any trick, which allows machines with Office 2k to run application build with Office XP?
Thanks in advance.
Pawel

Hi Cin
Yes, that is correct. The reason why I ask was how to find a solution so both XP and 2k can work in the same time.
You are right that most of the features for XO and 2k are simmilar, but try to use XP to open w 2k workbook from excel, it will fail.
cheers
Pawel

Similar Messages

  • 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

  • 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 (1.1.2) and 8.5

    I am not as crazy as I thought!
    I wrote a program today that collects data from excel reports in many directories using cell names and it worked well.  Unitl I saved it.  I had been saving the sub vi's, but when I went to close them I got a message about unsaved changes and I guess I clicked to save the changes today.  The program never worked the same again.  I would get errors like 41106 and 41110 at random (problems with excel not opening and other stuff).  I tried adding waits which slowed everything down and worked mostly.  But the only way to not drop data and get errors was to have a copy of excel open while getting my data.
      Well I just uninstalled/reinstalled the toolkit and rebuilt the vi that was having problems with the fresh install and everything is great again.  So my question is why does the toolkit have problems when I save it in 8.5?  The warning does say that the vi's are from 7.1 and I cant find any updates so I am hoping this is the latest version that came with my 8.5 suite.

    Hi Bryan,
    There should not be a problem with saving the VIs from the Report Generation toolkit in LabVIEW 8.5. I have checked the readme files to make sure but RGT 1.1.2 should work with any version of LabVIEW later than 7.0. However, the readme does discuss an specific upgrade issue. It says if you previously created VIs that use the built-in Report Generation VIs in LabVIEW Professional, Full, or Base packages or VIs from a previous version of the Report Generation Toolkit, installing the Report Generation Toolkit 1.1.2 might break the VIs you created. If the VIs you created contain any of the following VIs, edit them so they are compatible with the Report Generation Toolkit 1.1.2.
    Append Front Panel Image to Report VI—The Image Format input of the LabVIEW 6.1 version of this VI is a different enumerated type than the current toolkit version. Right-click the input and select Create»Control or Create»Constant from the shortcut menu to create a compatible control or constant.
    Append Table to Report VI—The connector pane position of the show grid lines input changed from the Report Generation Toolkit 1.0.1 version of the VI. Reconnect the original wire to the new input location.
    Get Report Settings VI—The cluster order of the font settings input changed from the Report Generation Toolkit 1.0.1 version of the VI. Right-click the output and select Create»Indicator from the shortcut menu to create a compatible indicator.
    Report Express VI—If a VI includes the LabVIEW built-in version of the Report Express VI on the block diagram, the VI breaks after you install the Report Generation Toolkit 1.1.2. Double-click the Report Express VI to launch its configuration dialog box, then click the OK button. Reconnect all wires to the Report Express VI.
    You might need to relink the following subVIs after installation because the connector panes changed in the Report Generation Toolkit 1.1.2. Right-click the VIs and select Relink to SubVI.
    New Report
    Dispose Report
    Append Front Panel Image to Report
    Append Hypertext Link Anchor to Report
    Append File to Report
    Append Horizontal Line to Report
    Set Report Font
    One thing that might have happened is if you had created the program in an earlier version of the toolkit, then saved it in the new version of the toolkit, maybe some of the upgrade issues regarding the VIs listed aboved cause LabVIEW to start giving you errors. Also, which version of excel are you using? After you re-did the VI program, have you tried to save it again and see if the same problem occurs?
    Carla
    National Instruments
    Applications Engineer

  • Report Generation Toolkit with Excel 2003 and Excel 2000

    Hello,
    I'm using the Report Generation Toolkit to generate an Excel report from an Excel template.
    The "NI_Excel.lvclass" is included in the "source" section of the application builder options.
    I create an exe file on  a PC where Excel 2003 is installed. On a Notebook, where only Excel 2000 is installed, the application crashes at the generation of the report:
    I guess the problem is the different version of Excel but I don't know. On the developer PC with Excel 2003 it works fine.
    In this document it's only talked about different Word versions.
    How can I use the Report Generation Toolkit here?
    I'm using it that way:
    Regards

    Oh, it seems that the Report Generation Toolkit "only" supports Excel XP/2003/2007.
    I think, that's the problem.

  • 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

  • Error 10 when building an application in LV8 and Report generation toolkit 1.1.1

    I am trying to build an application using LV8.0.1 and Report generation toolkit 1.1.1 and i get this error.
    Error 10 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
    Any ideas?
    Scientia est potentia!

    Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files?  I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs.  I think I've seen a similar post on the discussion forums in the past that recommended this.
    If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
    Good luck,
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • 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

  • Error building .EXE Report Generation Toolkit

    Whenever i try to build my application this error message shows up.... Error 1502 ocurred at AB_source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass: Save.vi
    it says the possible reason is Word_Open_Document.vi
       I'm using the report generation toolkit for office.... I really need to build this application soon!! 
    Please Help!!!
    Thx in advance
    Wong

    I finally made it work... As a reference, i upgraded from labview 2011 due to windows 8 incompatibility, and found that the installer kept showing these error messages. 
    I read in another post that if you opened the troubled VI and just clicked on the property nodes to browse and then ok, you just saved the VI, restarted labview and the error message disappeared. To my surprise IT WORKED!!!  I had to do it on several excell.llb VI's too. 
    Maybe you could report this bug in the report generation toolkit as a part of the NI team.
    thanks!!!
    Wong

  • Report Generation Toolkit on Vista and Office 2007

    Hi,
    I am trying to install Report Generation Toolkit 1.1.2 on LabVIEW 8.5 on a computer with Vista Business and Microsoft Office 2007.
    The installation is starting, but I am receiving a message saying that "Microsoft Office 2000 or later is not detected on the computer"
    The installation stops and the toolkit is not installed.
    What can I do ?
    Tom

    Tom SAVU wrote:
    Hi,
    I am trying to install Report Generation Toolkit 1.1.2 on LabVIEW 8.5 on a computer with Vista Business and Microsoft Office 2007.
    The installation is starting, but I am receiving a message saying that "Microsoft Office 2000 or later is not detected on the computer"
    The installation stops and the toolkit is not installed.
    What can I do ?
    Tom
    The Report Generation Toolkit does probably not support Office 2007 yet. This is because the Office ActiveX interface used to change with each version and the Report Generation Toolkit comes with specific libraries for each of the Office versions it supports. With the wrong office version the Report Generation Toolkit VIs are normally broken and can't run without some more or less involved modifications.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Report Generation Toolkit and Office 10 - build errors

    Using LabView 2011 and Report Generation Toolkit 2011.
    After installing Office 10, I would get build error for Excel-Print.Vi and Excel-SetCell.vi and build is then aborted.
    2011/vi.lib/addons/_office/_excelsub.llb/Excel-Print.vi.
    Says it is unable to save a vi without a block diagram.
    Uninstalled Office 10 and reinstalled Office 2003 and build went thru just fine.
    I can program using Excel 2003 and the compiled executable will work on another computer with Excel 2011 but once I install Office 10 on my LabVIEW computer I cannot build.
    Can't believe I could be the only one to experience this. Any workarounds?

    Duplicate Post

  • 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

  • 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

  • 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

  • Step By step procedures  for various scenarios Required ASAP!!!!!

    Hi All, Pls mail me the step by step procedure of the following scenaios. 1.) File-XI-File Scenario. 2.) Text file scenario. 3.)File to Idoc 4.)File XI- RFC.(R/3) 5.) BPM scenarios. any stuff related pls mail to [email protected] Thanks in Advance. S

  • Data Merge from Multiple image folders

    I'm on a MAC running CS3 and trying import several thousand images via DataMerge that are all housed in different folders. It is very difficult to move all the images to a single folder where the Tab Delimited File lives, which I understand is how I'

  • What do I have to do to print?

    I bought photoshop cs5 to print with my canon plotter imagegraf pro w8400pg. Does not print how do I have to set up or is there a plig in I need?

  • Create logfile from three vis - data is sometimes missing

    Hello, i have three measurement-vis running parallel in a loop The three results are continuously saved in  global-array and also in a text-file. The global-arrays has always all data but in the text-file is some data missing. I think this is because

  • Out of band config changes and CSM

      Were running CSM 3.3.1 SP1 on a windows machine.  We aquired a company and have found that they were making out of band changes without the use of CSM directly from the CLI.  Is there any easy way to sync the running config on the ASA firewalls to