01-04-2019 11:44 AM
@nickbike wrote:
@RavensFan wrote:
You talk about Excel 365.
Do you actually have Excel installed on this PC? Or is this one of those cloud-based versions where you are getting to Excel through a browser?
That's a good question. I do have Excel 2016 installed. I even tried to have Excel open already.
I also want to correct a mistake I made. I thought the Invoke node and the Right-click Export to Clipboard popped up Notepad on my old computer. I just tested it on a similar old computer and it didn't do that. It only copies the data to the clipboard it does not open and paste. I tried it on my current computer and the Export to Clipboard invoke node and right-click menu do work. I'm sorry for this mistake.
However, the original issue, Export to Excel, does not work either through the Invoke Node or through the Right-Click menu. The worse part is that there is no error reported. And even worse, I have a colleague that just got a new computer, LabVIEW 2018 and Excel 2016 and this works fine on his computer.
That sounds like an order of installation issue. As in, install support for.... which isn't installed.
01-11-2019 09:56 AM
I found a solution that fixed this issue. I was trying to build an EXE for another user and was getting the exact error and same broken VI as described in this forum post. https://forums.ni.com/t5/LabVIEW/Error-1502-Excel-Add-Reference-to-VBProj-vi/td-p/3617704
The fix described in that post of "quick repairing" Microsoft Office 365, not only fixed my issue on being able to build my EXE, but it also fixed my "right-click and export to Excel" and the "Invoke node export to Excel" issue.