Excel activex call changes between Office 2000 and Office XP. How does one manage that?

[pinkfloydwalsh]

I have several Active X calls from within a VI. One in particular is the Excel Cell Value property node in Office 2000. MS has decided to call it Excel Cell Value2 in Office XP.

I have built and exe on a machine with Office 2000 and can run the code on a machine with Office XP, but I can not build on the machine with Office XP. I can also run a VI with that call
on the Office XP box, but if I mass compile the VI I get the broken arrow.

I guess I am confuesed as to why it can run but not compile. If the ActiveX call is not there for the compile why is it there for the run? If I can expect this does it work in reverse where I
build on an Office XP box and run on a Office 2000 box?

[Andy F.]

These problems you are experiencing do stem from the ActiveX changes between Excel versions.  When you mass compile LabVIEW checks to see if everything is linked correctly, including ActiveX portions of your code.  Since there are slight changes the LabVIEW compiler detects something is wrong, but cannot isolate the problem.  You might need to force a recompile of that VI.  Check out this link.

https://www.ni.com/en/support/documentation/supplemental/12/debugging-techniques-in-labview.html

Hope this helps!

Andy F.