ActiveX VI recompiled whenever a calling vi is opened

[Larry_Stanos]

LabVIEW 8 insists on recompiling a vi I wrote to open a Microsoft Word document using ActiveX commands despite the fact that there have been no changes.  Consequently, a nagging dialog box pops up prompting to save this vi whenever I close it or any calling vi, or worse, when I try to build an application which includes it.  (See attachment for a demonstration.)  What is the cause for LabVIEW thinking that this vi needs to be continually recompiled and is there any way to prevent it?

Thanks!

Larry

[Elsa Fung]

It opened and closed fine for me (asked me to save the first time, then never after)

I have the same problem when I use ActiveX on Excel, but that's because I have 2 versions of Excel (Excel 97 and 2003) installed on my computer.  I think that's confusing LabVIEW which version of Excel library functions to use (the property and invoke functions have slightly different parameters).

So if you have two versions of Word installed, most likely that's the problem.

Hope this helps ^_^

See-Ming

[Larry_Stanos]

See-Ming,

Thanks for the tip.  However, I only have one version of MS Word installed (Office 2003) and I scanned my hard drive to verify that I only have one copy of MSWORD.OLB where the Word _Application object is defined.  I do have some older Office components installed (FrontPage 2002 & Visio Technical 5.0c), so perhaps there is another library that is confusing LabVIEW, but I'm not sure how to figure out what file that might be.

Thanks.

Larry

[Elsa Fung]

I right clicked on the Word Application reference constant and reselected the class (Word 11.0 object library), but I don't know if it'll solve your problem.

I attached the files with the reselected class, try it ^_^

See-Ming