I believe I know now why I'm seeing this behavior.
Network shared variables need to be read at least once in order to start subscribing to SVE (at least to work in a built application (.exe)). The network shared variables I was having trouble with were being read and manipulated as in the screenshot below:

Even though I initialized these 2D arrays, when read the FIRST time in the above code, I get back an empty array. Of course, executing the REPLACE ARRAY SUBSET in this case will give you an EMPTY array which is then written back to the network shared variable. Hence I got into a vicious circle and the network shared variable remains "empty" as well as the indicator to which it's bound.
I now initialize and immediately READ the shared variables (as shown below) before ever getting to the code above. This first read returns empty arrays, but "kick starts" the variables so the second read returns the value to which they were initialized (999.0) in this case. The REPLACE ARRAY SUBSET now has a non-empty array to work with and all is well.

(By the way, I got the three boolean indicators to work by removing their data binding and then reconnecting them again.)
Message Edited by Bill@NGC on
06-07-2008 05:30 PM