How can I have my program automatically confirm the validity of the Microsoft Word version?

[dj143]

With a built application, I am getting error -2146959355 when the system attempts to open a Word template file. Apparently this is due to a mismatch in the Word version. In this case, I developed the system on a computer using Word 2002, where the report toolkit is installed. I get this error on a computer with Word 2000. I can make an error trap to tell the user what this error means. However, I was wondering if there a better or more thorough or lower level method that the system can use to automatically determine the validity of the available Word version. It would be nice if after the application is installed that it automatically informs the end user that Word versi
on is incorrect. If this is not practical, it would be nice to inform the end user when the application is started. I�m using LV 7.1, Win2000, Report Toolkit v1.0.1. In case you�re interested, I just ordered Word 2003 so I can release the latest. When I receive it, I�ll install it and then reinstall the toolkit.

[Alberto]

Hi,
I believe the problem has to do with the different activeX classes of Word.
Try this small example that returns the Word application version ( for Word 2000 the returned version is 9.0). I don't know if this example works also for different Word versions (I only use 2000 version), try it and please let me know!

Alberto

[dj143]

With Microsoft Word open, click Help >> About Microsoft Word. The top line indicates the program version (i.e 2000, 2002, etc) and it also indicates in parentheses what I assume to be a formal version or release number. On my machines running Word 2000, the leading digit is 9.xxx where xxx represents variable numbers. On my machines running Word 2002, the leading digit value is 10.xxx. I assume that Word 2003 is 11.xxx, which would result in 11.0. I�ll confirm this later when I receive Word 2003. Thank you for the vi example.

[KileenC]

Great response Alberto! The Report Generation Toolkit is specific to the version of MS Office installed on a particular machine as a result of some of the changed ActiveX methods made in different versions of Office.

Hope this helps!

Kileen C.
Applications Engineer
National Instruments