I was wondering if someone could help me figure out why there is a difference between the two attached screenshots. The 'Excel Import Module' vi is broken when i open my source code on another computer. Both computers run labview 2010, both have Excel 2016, both have Excel Object Library 16.0. The broken one has Windows 7 and the other Windows 10. Not sure why the data type for VB Object changes between the two computers. Thanks all!
Normally that's what I would do bc I've had similar instances of this that I've been able to fix. This particular vi is one of those that it doesn't allow you to edit.
Hello, I'm having a nearly identical issue(my screenshots appear just the same as the original posters broken version, while my co-workers appears just like the good version). However, I cannot reselect VBproject in the Workbook property node without a workaround, and even then it doesn't fix anything. Although "VBproject" is checked, the option is grayed out. I can only select it by clicking "Browse" at the top and finding it there. Any idea what's going on?
I notice that "VBProject" is purple, as opposed to teal, which is what I would expect. I am using LabVIEW 2015 and Excel 2016 as well, but am unable to recreate the same issue you are seeing. My first suggestion would be to delete the property node causing the issue, and put down a new property node then rewire it exactly the same way as the "Unbroken VI" screenshot.
I had tried that previously and found that I could not recreate the previous property node. However, I reinstalled both the RGT and all of microsoft office, and the problem has resolved itself. I think there was an issue with my excel install, and so RGT was calling on a something from excel that didn't exist. Thanks for your help!
