excel easy text

[JohnBoy]

I am currently upgrading all our LabVIEW 7.1 programs to LabVIEW 2011.  The PC I'm working on has Windows 7 and MS Office 2010.

One of my programs uses Excel Easy Text function.  However, when opened in LabVIEW 2011, the error list shows Excel Easy Text.vi has a subVI that is not executable.  That SubVI is Excel Set Cell Color and Border.  Both of these functions are part of the LabVIEW 2011 Report Generation Toolkit for Microsoft Office, and have not been altered by me. This would appear to be a LabVIEW bug. Any ideas?

[RavensFan]

Any of the VI's dealing with Excel are probably using ActiveX functions.  The problem is that Microsoft makes changes to their activeX calls from time to time as they upgrade the Office apps.  Your LabVIEW 7.1 programs were written at a time when they made ActiveX calls to an older version of Excel.  (Office 2010 didn't exist at the time.)  Now that you are upgrading, your Office installation is a newer version, and some of those ActiveX calls have broken becasue they have changed between older Excel and newer Excel.  So the problem you have is not a bug with LabVIEW, it's the change in the installed MS Office codebase.

All you can do is look into the now broken VI's and fix the errors.  It will probably mean selecting the ActiveX calls and reselecting the functions (some function names may have even changed).  Or even deleting the original ActiveX functions and dropping new ones on the block diagram.

[JohnBoy]

It seems to me that the Report Generation Toolkit supplied with LabVIEW 2011 should have been upgraded by NI to take into consideration the requirements of Excel 2010. So while I agree this problem could have been caused by Microsoft changing the Excel Object Model in some way, I would expect LabVIEW 2011 to be able to handle those changes. I must emphasise this is all NI code, not mine.

[Matthew_Kelton · Accepted solution]

I see the same problem.  You can fix it by modifying the BorderAround Invoke Node and reselecting BorderAround.  It appears that the toolkit doesn't have the 2010 version of the call.  You'll notice an additional input willl be displayed.  You don't have to wire anything up, just reselect the BoarderAround Method.

[JohnBoy]

Thanks Matthew. That fixed it. Just another Generation Toolkit bug.