LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Strange bad wires

Hello.

I have some VI:s that I used with ActiveX and Excel 97, and LabVIEW version
5.01.
But, after the upgrade to Excel 2000, they are all "broken arrowed". Bad
wires everywhere.
Is ActiveX provided by LV 5.0 not compatible with the 2000?
Is there anything I can do to get it to work again?

I also have some VI:s using SQL under LV 5.0. There are no problems at all
with them
after the upgrade from Access 97 to Access 2000, and that makes me wonder if
I simply
have forgot something.

Concerning the ActiveX again, the built -in ActiveX LV example "Write Table
to Excel" seems to work also
with the 2000.
Maybe it has not to do with the 2000 upgrade? I have noticed before that I
suddenly found bad wires
on VI:s I open up. Then I correct the ba
d wire and save the VI. But next
time I open it up, the same
bad wire is there again! I do the same procedure, same thing over and over
again...

Thankful for any help / Per
0 Kudos
Message 1 of 5
(3,029 Views)
The active x libraries were probably updated when you upgraded to excel, but
your vi's are still pointing to the old activex libraries. You may need to
repoint your automation opens to the excel libraries.
"Per J" wrote in message
news:xVeP5.704$Sl4.2167@nntpserver.swip.net...
> Hello.
>
> I have some VI:s that I used with ActiveX and Excel 97, and LabVIEW
version
> 5.01.
> But, after the upgrade to Excel 2000, they are all "broken arrowed". Bad
> wires everywhere.
> Is ActiveX provided by LV 5.0 not compatible with the 2000?
> Is there anything I can do to get it to work again?
>
> I also have some VI:s using SQL under LV 5.0. There are no problems at all
> with them
> after the upgrade from Access 97 to Access 2000, and that makes me wonder
if
> I si
mply
> have forgot something.
>
> Concerning the ActiveX again, the built -in ActiveX LV example "Write
Table
> to Excel" seems to work also
> with the 2000.
> Maybe it has not to do with the 2000 upgrade? I have noticed before that I
> suddenly found bad wires
> on VI:s I open up. Then I correct the bad wire and save the VI. But next
> time I open it up, the same
> bad wire is there again! I do the same procedure, same thing over and over
> again...
>
> Thankful for any help / Per
>
>
>
>
0 Kudos
Message 2 of 5
(3,029 Views)
> I have some VI:s that I used with ActiveX and Excel 97, and LabVIEW version
> 5.01.
> But, after the upgrade to Excel 2000, they are all "broken arrowed". Bad
> wires everywhere.
> Is ActiveX provided by LV 5.0 not compatible with the 2000?
> Is there anything I can do to get it to work again?
>
> I also have some VI:s using SQL under LV 5.0. There are no problems at all
> with them
> after the upgrade from Access 97 to Access 2000, and that makes me wonder if
> I simply
> have forgot something.
>
> Concerning the ActiveX again, the built -in ActiveX LV example "Write Table
> to Excel" seems to work also
> with the 2000.
> Maybe it has not to do with the 2000 upgrade? I have noticed before that I
> suddenly found bad wires
> on VI:s I open up. Then I correct the bad
wire and save the VI. But next
> time I open it up, the same
> bad wire is there again! I do the same procedure, same thing over and over
> again...


What you are seeing is that the ActiveX functions for 97 and
2000 versions of Excel are different. The newer version of
Excel should support the older formats, but unfortunately,
older versions of LV would automatically try to get the
latest version.

If you want to continue using version 5 of LV, open the
diagram, find the Open node for the Excel connection, and
reselect it. This may fix some or most of the wires. If
there are others, reselect the properties or methods.
There may be new parameters or outputs.

Greg McKaskle
0 Kudos
Message 3 of 5
(3,029 Views)
Thank you

However, I've tried to replace and reselect, but when i wire the
_Excel_Worksheet reference to the new property node,
it won't change from the initial "Property" to "_Worksheet" as I'm used to.
Some things seems to work at other places in the VI, also other worksheeet
properties, but they have other things selected.
It doesn't like "Columns" and "Rows" any more!

I can't select other properties either, anywhere ( "No Properties" !)

I have a simple open procedure with Automation open - Excel application -
"Visible" property, that seems OK.
But I can't do another one!

ActiveX is activated also in the References. I can't free myself from the
belief that I have forgot something silly here.
And when I'm freed, then I would confront the idea of having to buy a new LV
version only because I upgraded Office.
Should the new install of Excel also be "activated for ActiveX", any way?

Greetings /Per





Greg McKaskle skrev i
diskussionsgruppsmeddelandet:3A0F2B94.5F4FD4C@austin.rr.com...
> > I have some VI:s that I used with ActiveX and Excel 97, and LabVIEW
version
> > 5.01.
> > But, after the upgrade to Excel 2000, they are all "broken arrowed". Bad
> > wires everywhere.
> > Is ActiveX provided by LV 5.0 not compatible with the 2000?
> > Is there anything I can do to get it to work again?
> >
> > I also have some VI:s using SQL under LV 5.0. There are no problems at
all
> > with them
> > after the upgrade from Access 97 to Access 2000, and that makes me
wonder if
> > I simply
> > have forgot something.
> >
> > Concerning the ActiveX again, the built -in ActiveX LV example "Write
Table
> > to Excel" seems to work also
> > with the 2000.
> > Maybe it has not to do with the 2000 upgrade? I have noticed before that
I
> > suddenly found bad wires
> > on VI:s I open up. Then I correct the bad wire and save the VI. But next
> > time I open it up, the same
> > bad wire is there again! I do the same procedure, same thing over and
over
> > again...
>
>
> What you are seeing is that the ActiveX functions for 97 and
> 2000 versions of Excel are different. The newer version of
> Excel should support the older formats, but unfortunately,
> older versions of LV would automatically try to get the
> latest version.
>
> If you want to continue using version 5 of LV, open the
> diagram, find the Open node for the Excel connection, and
> reselect it. This may fix some or most of the wires. If
> there are others, reselect the properties or methods.
> There may be new parameters or outputs.
>
> Greg McKaskle
0 Kudos
Message 4 of 5
(3,029 Views)
I have seen the same behaviour when I tried to translate DAO routines (MS access) into LV6. Things like DAOrecordset.field.value can not be accessed anymore through the lv active-x nodes and a lot of broken wires result. This example used to be called "collect". This is NOT because a new version of a microsoft product was installed, but because somehow labview LOST some functionality going from 5.1.1 to 6.0.2.
0 Kudos
Message 5 of 5
(3,029 Views)