Cannot open reference to Word in "New Report.vi"

[James@Home]

I am trying to fill a Word template, but cannot get past an error inside the New Report.vi.

The Automation Open subVI returns the following error:
Error -2147312566 occurred at Error loading type library/DLL.
in New Report.vi

This error code is undefined. No one has provided a description for this code, or you might have wired a number that is not an error code to the error code input.

The previous error is replaced within the New Report.vi with this error:
Error -41106 occurred at New Report.vi

Possible reason(s):

Report Generation Toolkit: Microsoft Word or Excel did not open. Make sure Microsoft Word or Excel is installed.

The New Report.vi works without error for Standard Report, HTML & Excel report types.
I have removed/reinstalled Office(97) and the Report Generation Toolkit (1.1); no improvement seen.
FYI: LabVIEW 7.1.1

Does anyone have any suggestions for debugging the cause of this error?

Thanks for any suggestions,

James

[Philip_Courtois]

Hi James,

The behavior that you are describing has previously been reported for Report Generation Toolkit 1.1 with Microsoft Word 97 SR2 (Service Release 2). I haven't seen the error reported with SR1, so a removal of the SR2 update might cure the issue.

Other workarounds for this issue includes to use version 1.0.1 of the Report Generation Toolkit instead, or to upgrade your version of Microsoft Office. It may also work to force-recompile your VIs. Open the VI and press CTRL-SHIFT-Run. This may suddenly make the VI broken. Now click the broken Run arrow to display the error list. Find each property node that is broken and attempt to re-select the same or similar property from the list.

Please let me know if you are able to get it to work by using my suggestions, thanks.

[James@Home]

Philip,

Thanks for the suggestions.

I must use Word97, it is the version on 30+ target test systems.
I recompiled after installing the 7.1.1 updates, but tried it again anyway.
Then, I found my Nov03 CD Kit and replaced the Report Generation Toolkit with Ver. 1.0.1.
That seems to be a satisfactory workaround for the present time.

Thanks again for the suggestions,

James