Screen Function File Accessor Behaviour |
DEVELOPER |
 |
|
Screen Function File Accessor Behaviour |
DEVELOPER |
|
PROIV Developer mandates that all field objects have unique tag ids. In native PROIV it was possible to specify a file read return field that was subsequent to the boundaries of the cycle in which the file was read. PROIV would gen the function successfully. The runtime behaviour would be that the timing cycle would complete (including the write pass) but all subsequent file reads and fields visits would not take place. This behaviour is the same as specifying the return field to be a dummy field as the last field in the cycle. Thus the CycleExit option was introduced into PROIV Developer to support the legacy behaviour.
Name - The name of the file to be accessed.
Primary File for Cycle - Check if this file is to be the cycle’s primary file.
Sort/Paint Pass Options
Include in Sort/Select - Check if this File Accessor is to be included in the cycle’s sort/select pass.
Suppress Read During Paint Cycles - Check this box to suppress reading of file while screen paint is in progress.
Return Field Options
Exit Cycle/Return Field - Choose whether a read error on the file will exit the cycle or move the cursor to a specified field.
If Return Field is chosen, then select the field tag (from the drop-down list) for the cursor to move to on a file read error.
Read Modes for Screen Modes
Add/Change/Look/Delete - The modes in which the file is to be accessed when screen is in Add/Change/Look/ Delete mode.
Topic ID: 500355