Some of Point Beach RO's have curly braces in the RO return value for the units in P/C. Found this on some (5-7) Annunciator RO values. The definition of the return value (multiple return values) uses curly braces so PROMS cannot distinguish between brackets being part of a unit value or part of the format for multiple return values.
Equipment Designation, Main Steam (MS), Annunciators have examples of return values with curly braces. Look at the Referenced Object Definition on the Annunciators tree node for the definition of the return value.
Refresh issue in RO Definitions. Modify an In Use field item that is not one of the Standard items, choose Continue, choose OK in the Text Definition Field. when prompted if want to Update Local or Generic definitions:
1. Prompt should contain table name (previously was not for Setpoint items)
2. If Select "Yes", Should refresh to new field name when return to previous screen / click ok to go back to RO Definition.
When updating a field in a RO Definition, there is a prompt asking if changes should be Local or Generic --- Should change wording to explain that Local is local to that table (and include Table name in that wording)
After converting the Robinson ROs to SQL, upon changing an In Use field and clicking Continue, an "Error on Schema" message box displayed with an unhandled error exception.
In creating a temporary (meta) file for Complete RO Report, file was sometimes not created anew with the FileMode.Create setting. Changed to FileMode.Append and specifically delete the meta file before calling to generate it.
