report generation toolkit problem with office 2000 and office XP

[gosenbach]

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

[Philip_Courtois]

Hi Greg,

If you want to distribute an application that uses the "Report Generation Toolkit for Office" functions, then you have to make sure that the version of Microsoft Office is the same on the development machine as on the target machine.

Best regards,
Philip C.
National Instruments
There is currently no way of simply choosing what target version of Office that you want your application to work for.

Please refer to this KnowledgeBase that describes a similar situation with the version 1.0.1 of the toolkit.

[Acer]

Am I reading this correctly in saying that i would need to uninstall office xp and reinstall office 2000 on my development system and recompile the .exe?

I have the same exact situation, actually except that I am developing/building the application on a computer with office 2003. The target machine is windows 2k w/office 2k.

What exactly would be the appropriate steps to take here? I have reinstalled the report generation toolkit with office 2000, xp and 2003 support files checked. Would I just have to recompile the .exe on a machine that has office 2000?

Thanks,
Acer

[Philip_Courtois]

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!