Connection errors associated with the property node

[Hef]

I installed LV 6.1 on a new PC running windows 2000. Next, I copied an existing VI (that is running fine on a PC running win 95 and LV 5.0) to the new PC.
However when opening this VI on the new PC, it opens with the error "you have connected two terminals of different types". These errors are associated with a sub vi called "excel AE", and always occur wherever the Property node is used in this sub vi.
I am confused as to why the VI works on the old PC running LV 5, but will not work with LV 6.1. I did not write this VI and I am new to LV. Any help for this newbie would be appreciated. Thanks

[Michael_Munroe]

What version of Excel is on the two PC's?

It sounds like the new PC does not have MS Excel installed, or has a newer version. The VI probably uses the ActiveX interface of Excel 5.0, which is not compatible with Excel 2000+.

If you don't have Excel, you will need to install it on the new PC. If you install a much newer version, then reconfigure all of the problem method and property nodes. The easiest way is to first change the automation refnums to the current version of the same level. Then select the appropriate property of each of the nodes. Some additional rewiring may be required.

[ole]

The problem is that MultiUserEditing outputs a boolean and Accessmode requires a long (integer). You will have to put a case in between to give AccessMode the correct input, probably xlShared when MultiUserEditing is true. Right click on the item to access help. Look into the working version to get an idea. I think the problem is more related to different Excel than LabView versions

[mikeporter]

Here is a copy of your VI that addresses both of the issues in the other two posts. Note that I haven't tested it all out so I don't know if it works exactly the same as the original version.

However, this VI has some real problems. First, the error handling in it is poor to non-existent. If it works no-problem, but if it ever doesn't work you'll have a major effort in figuring out what's broken. In addition, it will hide errors that occur before it in the calling VI.

Second, I suspect that given long enough, this VI could produce a memory leak as many secondary references are opened that are never closed.

Mike...

[Hef]

The new PC had Office XP, the original PC has excel 97.
I uninstalled Office XP and installed Office 2000 on the new PC,hoping that the excel version of 2000 would be more compatible with excel 97. Unfortunately,the same errors occur with Office 2000 installed.

[Hef]

Mike thanks for editing that VI for me, as that corrected the errors I was getting. Unfortunately, I am now getting a 10401 error,("device is not a NI device, the driver is not installed or the device is not configured") which I believe has something to do with configuring the NI PCI-MIO-16E board I installed on the new PC. The board is showing up in automation and explorer under devices but perhaps it is not configured correctly?
By the way, to correct the VI did you have to go to each property node and make a change?

[mikeporter]

Yes, the error you're getting is realated to the DAQ. Talk to NI, to troubleshoot that. And yes, I had to go do something to most of the property nodes. The biggest thing was changing the automation references.

Mike...

PS: Don't forget the problems I pointed out in this code...

[Michael_Munroe]

Here is your VI modified for Excel XP compatibility. Replace all instances of the old VI with this one and give it a try.