"Conn Execute.vi" Comes up broken...

[steve05ram360]

From the Connectivity, Database, Utility palette, the Conn Execute.vi comes up broken when I place it on the block diagram.  Has anyone else run into this?  and what was the fix?   LV says I have a wire class conflict when coming out of the "forward-only" case statement

any help here would be greatly appreciated...

TIA

[lmtis]

Why are you connecting a method output to a reference input? 

[steve05ram360]

this vi came from the Database Toolkit from NI.  It was as is when I tried to use it.  It was broken from the start.

[lmtis]

What version of LV?  I don't have that VI so I assume it must be newer than 8.0.  If not, can you post it?

Message Edited by lmtis on 11-29-2007 01:50 PM

[steve05ram360]

it is in this lib...

[steve05ram360]

oops, sorry, it's LV 8.5.

[griffindore]

Hi Steve,

When I open the VI you provided, I do not get any broken wires or a broken run arrow. From the picture you provided, it appears that your LabVIEW installation thinks it's connecting wires of 2 different data types. Could you turn on your Context Help and post what the data types are? Thanks.

[lmtis]

Mike,

I agree.  As I said in my first post, his picture shows the execute output of a _connection method connected to a reference input.  I don't have 8.5 so I can't test it, but I think he needs to delete the broken wire and connect the reference output of the _connection method to the output of the case structure (and thereby to the reference input of the recordset property node).

[steve05ram360]

hummm... shut everything down over the weekend, fired it up this morning and problem is gone.  makes me think that one of the previously loaded vi's may have been causing a problem with it...???  doesnt make sense.  Seeking another solution friday, I found a global variable that someone created that had all of the data table colums listed as part of a cluster/array...  So at this point it looks like I'm good to go.

I will try to recreate the problem later in the day... if I'm sucessful and can figure out what's going on, I'll post any findings back here.

[griffindore]

Thanks Steve,

If you can reproduce this, it would be good to hear what steps you took to create the problem.