Applies To:
  • CitectSCADA 5.00
Summary:
When [Page]RangeCheck is set to 0 (default) the #RANGE error still appears for the object when the value is out of range.

When [Page]ComBreakText is set to zero and range checking is enabled and the value is out of range dynamic text objects do not appear hashed like other dynamic objects. 

Solution:
CIT has confirmed this to be a problem in Citect for Windows versions 5.00. This problem has been fixed in version 5.01. 
Keywords:
 

Attachments