Applies To:
  • CitectSCADA
  • Alarm Paging System Database

I have configured a number of paging alarms via the Paging System Popup Page. I have confirmed that these alarms have been added to the PagingV3.mdb. I start my project and have been paged successfully. However, not all of the alarms I configured as Paging Alarms work. If I look in the PagingV3.mdb I discover that these records have been removed. Why is this?  

When the paging system starts it cross checks the alarms configured to be paged with the ones in the Citect database. If any of these alarms are configured using a Citect Area then the cross check function does not see them and removes them from the MDB file. You can avoid this by doing the following:

Instead of running PagingSystemStart() in the Startup code run:


where the User "Paging" has no password and can view all areas in the system.