Control Tables

• Code (field CTL)

This code identifies the created records in a unique manner.

• Description (field DES)

• Mandatory field (field OBL)

This information indicates whether the field is mandatory or not. For an alphanumeric field, mandatory signifies that the zone cannot be empty. For a numerical field or date type, mandatory signifies that a nil value cannot be entered.

• Condition (field CTLOBL)

If the Mandatory box is checked, it is possible to add an additional condition. If the condition is empty or the result of the condition is true, the field is mandatory. If not, a null value can be entered.

• Execution (field EXEACT)

This field is used to define the context for the use of the control table :

• Interactive signifies that the control is only made on entry (whether in client-server or Web mode)
• Import/Web service  signifies this this control is only carried out if the user is not available.
• Always signifies that the control is always carried out.

• Control type (field TYPCTL)

The control type (which can be None if all the required controls have already been defined in the header or in the previous tabs), can also take the following values :

• mandatory value : only one of the values defined in the control table is authorized.
• prohibited value : all values are authorized, except the values listed in the control table.
• value range : the authorized values are defined within a range.
• table reference : the value must correspond to a principal key value in a table defined elsewhere.
• expression : a logic expression must be verified by a control value.

• Dependency (field DEPCTL)

This field is only entered if the type is mandatory value.

In this case, it is possible to link the choice list proposed to a choice previously made for another field in the same screen, itself controlled by another control table to whom the code is given, and which uses in one of its controls a first choice list.

It is then possible to associate, in the values table that follows, a value controlled by one of the values in the linked control table (if no value is entered in the dependent value column, the code entered can be used irrespective of the value controlled in the dependency table).

This mechanism is similar to the dependencies defined in themiscellaneous tables, but it introduces a constraint: in fact, this type of "dependant" table can only be used in the control table allocation in screen management (by entering a value in the column control table, a window opens, in order to enter an expression defining the control value in the context).

• List of values (field LSTVAL)

Entered in this table, is the exhaustive list of authorised or prohibited values, according to whether the control type is Mandatory values or Prohibited values. Up to 30 values can be entered, with a dependence value if the control table is linked to another control table.

• Dependent values (field DEPVAL)

Used to indicate the values corresponding to the dependence table.

• Start range (field DEBUT)

These fields are used to define a minimum and maximum value between which the data must fall, when the control type is Value range. These ranges can only be numerical values.

• End date (field FIN)

• Table (field REFTAB)

When the control is of the type "table reference", the controlled field must correspond to a value of a table key, which is defined here The key used is that defined by the first table index (which obviously must be defined).

• Expression (field FRM)

When the control is of the Expression type, a logic expression is defined here that must be true in order that the control is considered as carried out. The current value to be controlled is defined by the VALEUR variable. In this way, miscellaneous expressions can be inserted with the aid of the formula editor. For example :

• Error message (field MSG)

The error message that will be displayed if the control is not complied with is entered here.