During a TCP network activity in LabView 2013, a variable can not be used to hole the connection ID. This worked in LabView 2013.

[mlwarren]

I recently upgraded to LabView 2013 from LabView 2012.  In LabView 2012 I often used a global or local variable to hold TCP network connection IDs.  But in LabView 2013 a global or local variable does not seem to have the ability to hold a conneciton ID.

Has anyone else seen this issue?

I have attached an example that fails when the VI is run the 2nd time using the Global variable to hold the connection ID.

Any help would be helpful.

Thanks

Matt

[altenbach]

I might be wrong, but I would not expect for a connection ID to survive between different runs. Why do you need this?