Behavioral differences, no, but we prefer something like the latter approach because it's more understandable when you are using Select to find your way through the system, and more documentable (is that a word?) in general. I have writes directly to CALC block inputs from graphics in one of my systems now and it's a PITA. If the CALC block code is not commented (and you have to go into ICC or some other tool to see that, too), you have to go to some other tool to see that it is being written from a graphic. Corey Clingo BASF From: "Johnson, Alex P (IOM)" <Alex.Johnson@xxxxxxxxxxxx> To: "Kalpesh, Jagdish C" <jckalpesh@xxxxxxxxxxxxx>, "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx> Date: 06/25/2012 09:56 PM Subject: Re: [foxboro] Set Text in Fox view Sent by: foxboro-bounce@xxxxxxxxxxxxx Assume that the two target block parameters are: 1) C:B.P and 2) C1:B1.P1 I would have my FV display/overlay, write its value to C:B.P (or C1:B1.P1) and have C1:B1.P1 connect to that data source. For example, assume that the targets are CALC blocks and you are using the ICC. In that case, FoxView would write to C:B.RI01 and the input of C1:B1.RI01 would be C:B.RI01. This second connection would look something like this in the ICC: NAME B1 TYPE CALC ... RI01 C:B.RI01 ... This is very effective since it is likely both targets are in the same CP. The only other reasonable approach is to create a block specifically to hold the value (C:B.P; a Data block is typically used) and connect both C1:B1.P1 and C2:B2.P2 to that Data block. In practice, I can't think of any behavioral difference between the two approaches. Regards, Alex Johnson Invensys Operations Management 10900 Equity Drive Houston, TX 77041 +1 713 329 8472 (desk) +1 713 329 1600 (operator) +1 713 329 1700 (Central Fax) alex.johnson@xxxxxxxxxxxx<mailto:alex.johnson@xxxxxxxxxxxx> _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave