Invoke ActiveX Node with Microsoft Word conflict

[Zing]

I have a stable LabVIEW 7.0 application that uses “Microsoft Word 9.0 Object Library Version 8.1” to edit word files. After changing my development system computer, the “Documents.Open” method no longer works. The error is “The server threw an exception -2147417851”. It appears to have added the following inputs: NoEncodingDialog, DocumentDirection, OpenAndRepair, XML Transform. See the attached old and new code images.

I’m running the same version of Word 2000 (9.0.2720) and LabVIEW. The only change is that I have installed Outlook 2007 and I suspect that this is the problem.
 

Does anyone know how to find the corresponding DLL for a ActiveX control used in LabVIEW as I might be able to copy it from the old PC or has anyone had this problem before and managed to open a Word document. Cheers, Victor

[BadgerSoft]

The MicroSoft Word ActiveX architecture is a always moving target.

The quantity of arguments passed changes often and because of the distributed nature of Windows, one program can deliver a low level change unrelated to the application you are working on.

The good news is, after you compile your code to an exectuable, additional optional arguments that you do not have in your code does not through an error.

The bad news is, when you are developing, you do need to force the ActiveX properties and invokes to update or it will appear broken.

I have 100s of vis that automate Word and Excel.  Updating the development environment is always a 1 day adventure ... discovering what is new from MicroSoft.

Also keep in mind that MicroSoft is backwards compatible.  If you are distributing, don't develop on the latest greatest and assume it will work on older versions of MicroSoft.   You need to develop on the oldest version of MicroSoft you intend to support and the newer versions will work too.