Level 2 generation in native access mode
These instructions correspond to the validation of modified records in graphical lists, and to instructions updating database files with data entered in the screen.
The updating instructions are generated according to the data flow analysis.
Note: When the logical entity has a default logical server, the instructions related directly to the entity will be assigned automatically to the logical server, except in the SFTKYS_PROCESS.
In the example below, <S1> is the default logical server of ENTITY1, and <S2> is the default logical server of ENTITY2.
Typical structure
******************* VALIDATION xx *******************
* For the window BEGIN_STD <S1> < generation of the VP-class management rules for non-list fields > <S1> PLACE VIEW_A <S1> < generation of the VE-class management rules for the entity corresponding <S1> to VIEW_A > <S1> CLASSIFY VIEW_A END_STD
* For a list READ_LST <window.object:list_prop> *MODIF BEGIN_STD <S2> < generation of the VP-class management rules for the list fields > <S2> PLACE VIEW_B <S2> < generation of the VE-class management rules for the entity corresponding to <S2> VIEW_B > <S2> CLASSIFY VIEW_B END_STD END_READ_LST |
Notes: As regards VP-class management rules, the $PROP (properties) displayed on the screen will be replaced by screen field guide words; otherwise, they will be replaced by file field guide words.
As regards VE-class management rules, the $PROP (properties) are replaced by file field guide words.
Important: When referring to "screen field guide words" with VADELIA or MADELIA programs, it corresponds to the value property of the graphical object (the "screen field") or, if the graphical object has one, to the name of its associated variable.
With WADELIA programs, this is the graphical object's name.
Click below for further information about: