Control of dependencies
It is possible, when using several miscellaneous tables in a screen (for example to define the groups and sub-groups in the database records), to create dependencies between tables. A dependance is characterized by :
- a dependent miscellaneous table number defined in the parameterization of the table.
- a link (optional) for the codes of the dependent table to a code in the source table (ie a link from the subgroup to the group that characterize it).
An annex documentation explains the detail of how this functions.
When the dependencies have been created, they are tested in real time on entry. But when the modifications have been made (add a dependence, modification of a link), the control is not carried out in real time on the group of existing records.
It is for this reason that this dedicated function exists. It carries out a control, which can be long, on all the data using the miscellaneous tables with links, and returns a list of any anomalies in a log file.
Start confirmation
No entry screen is presented on the launch of this function, only a confirmation box.
Contents of the log file
The log file contains the lines of the following type :
[TABLE_CODE] ( [TITLE_OF_THE_TABLE] ) Miscellaneous table [NNN] Fields [FIELD_CODE]
Code [XXX] incompatible with the dependance [YYY] : [CURRENT_KEY] [RECORD_TITLE]
With :
- The first line appears in the control header for a field in a table if there is at least one error :
- [TABLE_CODE] and [TITLE_OF_THE_TABLE] corresponding respectively to the code and the title of the table in the dictionary.
- [FIELD_CODE] corresponds to the field (controlled by miscellaneous table number[NNN]) in which the error has been found.
- The following line is repeated for each erroneous record :
- The code [XXX] is the value of the current field.
- The code [YYY] is the value that it must have if the dependence rule had been respected.
- [CURRENT_KEY] and [RECORD_TITLE] identifies the record in which the error is produced.