Built in Excel Broken Vi's

[spforster]

I'm having difficulties with a new Windows 11 computer whereby several VI's are not working anymore but then worked on the previous Windows 10 computer. I've uploaded some images of one of the Vi's that isn't working, an Excel Set Font Vi where by one of the wire connection won't connect anymore as it says there is a mismatch of data type.  I've put the same Vi on a second Windows 11 computer and they are working fine.  Any help in finding where the issue may lie would be greatly appreciated.

Simon

[aputman]

Are the versions of Office the same on both PCs?  Is your version of the toolkit compatible with the version of Office on that PC?

https://www.ni.com/en/support/documentation/compatibility/17/report-generation-toolkit-and-microsoft...

I'm using Labview 2018 and the only file I could find was Excel_Set_Font_Range and it's slightly different than what you show. 

[spforster]

They are both Office 365, but it looks like its slightly different versions.  Only problem is I can't install a different version as it automatically gets installed by the company.

[aputman]

If you right-click on that Characters->Font property node, is there an option to relink it?  Invoke nodes can sometimes get bugged and have to be relinked.  I assume property nodes can also get bugged.  You could also try creating a new property node. 

Reference: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019N7CSAU&l=en-US

[spforster]

I don't think it's the Vi as it's the same file that I use on the other Windows 11 computer, as they're in a shared folder across the two.  Would there be anything else causing this Vi and other Vi's to not work like this?

[aputman]

I don't understand what you mean.  Excel Set Font is a built-in VI.  It shouldn't be on a shared drive.  Did you try what I suggested?

[spforster]

I know it's a built-in Vi, I just moved it to prove a point that it works on one of the Windows 11 computers but not the other one.  Like I said, it's not the only Vi that is having issues like this.  I won't be able to try that out until Monday, when I'm next in the office, as the computer doesn't support screen sharing.

[aputman]

You have a few options:

• Manually relink the broken invoke/property nodes, as I already mentioned.
• Reinstall Office
• Use the mass compile function on the RGT VIs.

All of these are discussed in the link provided. 

[spforster]

Thanks, I'll try that out on Monday.

[BertMcMahan]

---

@spforster wrote:

I don't think it's the Vi as it's the same file that I use on the other Windows 11 computer, as they're in a shared folder across the two.  Would there be anything else causing this Vi and other Vi's to not work like this?

---

I don't think you should do this. Those are "built in VI's" in the sense that they ship with LabVIEW, but they're actually just accessing the Office function calls under the hood. Different Office versions will link to those files differently. Sometimes, these links break, and you need to relink them (see the link given earlier in this thread).

So, if you have different Office versions on the different computers, they won't link correctly. You may be able to fix this by ensuring all of these VI's have "Separate compiled code" checked, but I'm not sure.