Re: [foxboro] delete & undelete

Well, folks, as near as my years of FoxSperience can
figure, this process does exactly as the name implies.

First the block is deleted; completely removed from the CP,
OM lists, CSA, and so forth.  Next, the block is compiled
into the CP etc. as if it were a brand new block being added.

The trick is that the CIO Config saves a copy of the source
of that block in a temporary buffer before the delete.  That
copy of source is used to do the compile from source that
is the "undelete".

Note that this also means that any block parameter where the 
value in the CP is different from the one that CIOCFG sees
will be set to the value that CIOCFG had before the 
delete-undelete was performed.  It also means that the block
position in the CP image and other placed has changed, hence
a display with the block on it is likely to need to be called
up on screen again for re-optomization.

Regards,
William C. Ricker
FeedForward, Inc.
Marietta, GA, USA
wcricker@xxxxxxxxxxxxxxx
770-426-4422  

 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: