Check External References

The elements in some types of Database (DB) have reference or reference array attributes which can point to elements in other DBs.

If the NOCHECK option is set, Data Integrity Checker (DICE) does not cross-check any references to other DBs. It is recommended that this setting is always used for Transaction databases.

If CHECK is set, each referenced element is checked to see if it is a valid type. A non-fatal error message is produced for each invalid external reference found. The following tests are applied to each external DB to which reference is made:

• Does the referenced DB still exist?

• Is the referenced DB a valid type? For example, a reference attribute in a Model DB which points to a Draft DB must be illegal.

• Is the position pointed to within the limits of the referenced DB?

  Note:
  For a copied DB, DICE only checks that the reference is within the limits of the largest copy.

  A non-fatal error message is produced for each invalid external reference found.

Not recommended for Transaction databases due to the large number of errors that will be reported.

The REJECT option should normally only be used when the user is certain that the database which is being checked should not contain any external references, for example, to a Dictionary database. If this command is used, any external reference found in the database will be reported as a fatal error and further checking will be abandoned.

Not recommended for Transaction databases due to the large number of errors that will be reported.

If databases have been copied, the references will be checked against the first copy found.

If the user specifies the EXTERNAL CHECK option, they can specify a Preferred MDB. In this case, DICE will check external references to databases which are current within the given MDB, before checking other databases in the project. This option is mainly relevant when extracts are used, which means that there may be many databases with the same database number in the project.

The EXTERNAL REJECT option should normally be chosen only when the user is certain that the DB which is being checked should not contain any external references. If this setting is used, any external reference found in the DB will be reported as a fatal error and further checking will be abandoned.