LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with GOOP Excel Toolkit in Labview

Hi, all,
 
I have a Labview program using GOOP Excel Toolkit. I import some data from a text file into Excel file, then save the Excel file using the path and file name I input.  This program is working fine on one computer, but when I copy this file to another computer, the run arrow becomes broken. The error message shows that in one of the SubVI of GOOP, Excel Save.vi, "Invoke Node: contains unwired or bad terminal". Below is the picture of excel save.vi. I did not change any wire in that SubVI, somehow it becomes unexcutable on the new computer.
 
Did any one have this problem before? How to solve this problem?
 
Thank you very much.
0 Kudos
Message 1 of 6
(3,489 Views)
Anyone? Thanks.
0 Kudos
Message 2 of 6
(3,468 Views)
My guess is that this problem is related to ActiveX automation not working properly the same way in the two computers. I assume that the toolkit you are using requires ActiveX (or .NET) class to access Excel. The version of this ActiveX class installed on the two computers may differ. Try to find the open automation node in your program that actually creates an object of ActiveX excel class. I guess this is the point int your program that is broken. Once you have found it you can figure out what dll does it link to and see if the same dll is present in the other computer.

Tomi
--
Tomi Maila
0 Kudos
Message 3 of 6
(3,462 Views)
Hi J3000,

I'm assuming that you are talking about the "toolkit" linked here. If so, it was actually developed by a 3rd party, Philips Research, so it is not supported by National Instruments. There is some contact information for the author at the bottom of the readme file included with the package, so I would recommend trying your question there. I've posted it below for your convenience:

Philips Research COS/TMA
email: martin.vernhout@philips.com


Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
0 Kudos
Message 4 of 6
(3,462 Views)
Hi Tomi

You are right, this has to do with the different versions of excel.
Microsoft was so nice to change the names betwen the different versions.

Wich version of excel gives the problems.
I probably can send a correct version, if you name the excel version.
greetings from the Netherlands
0 Kudos
Message 5 of 6
(3,457 Views)
Hi, thanks for the information.
 
The original computer has Excel 2002. The program stopped working when it is running on the new computer with Excel 2000.
 
 
0 Kudos
Message 6 of 6
(3,453 Views)