Supervisor utilities > Relations

Recover functions are all related to the Relation Management files, F90 (containing codes for persons and companies), personen (persons) and firmas (companies).

These functions can be started from the Supervisor menu, option Recover functions.

In the appearing screen five different functions can be activated and will be described below.

1. Recover table numbers

2. Recover F90

3. Delete empty table codes

4. Delete empty relation codes

5. Delete floating records

All functions can be activated together by activating all check boxes.

Important: Before executing one or more functions, make a back up first!

1. Recover table numbers

This functions checks all table numbers in existing files of Relation Management. If necessary, these table numbers will be recovered on the basis of table numbers in the file layout.

2. Recover F90

All entered persons and companies are saved in the file F90. This file is built up on the basis of the files "Personen" and "Firmas". This function compares the values in F90 with the files for persons and companies. If values of F90 appear in these two files, values found will be copied to F90. If the values of F90 do not appear in the files for persons and companies, values will be copied to the two files.

Next, codes in the files for persons and companies will be compared with codes in the F90 file. If codes do exist in the files for persons or companies, and do not exist in F90, new records will be created in F90.

3. Delete empty table codes

In Relation Management, tables can be maintained by the user. For example, in the file "Contract partners", the type can be maintained in a list. The entered code and description will be saved. The table number and the description of this type will be saved as well.

If this function is executed, Mill7 checks if records exist with no table number. If such records exist, they will be deleted.

4. Delete empty relation codes

With this function, records in the files for persons and companies will be checked if the code field has a value. If not, the record will be deleted.

All Relation Management files will also be checked. Records with empty client codes will be deleted.

For each record in the Relation Management files, a field for a unique creation code exists. Record with notes in the memo file are referring to these creation codes.

The creation codes will be made unique if duplicates are found. The creation codes in the memo records will be changed accordingly.

5. Delete floating records

This function checks for records in files that are related to parent records that are not present. This concerns, for example, event details that refer to a non-existent event. The causes of this type of situation can vary, but it comes down to the fact that a process has not been fully executed, for example because an error has occurred. If an event needs to be deleted, the records with the details must also be deleted. These are separate steps. If an error occurs during the deletion of the parent record or shortly thereafter, it may happen that the child records, the event details in our example, are not deleted. They then continue to "float". To prevent them from accidentally being connected to a newly created parent record later on, it is wise to delete floating records. For that reason, it is recommended to perform this function from time to time.

If there are records in these files whose relation code does not appear in file F90 (Firms and Persons), this record is considered a "floating record". Performing this function will delete this record. Therefore, if this function is executed, the function "Restore F90" must be executed first. This function is selected automatically.

Floating records can also appear in other files, such as notes, documents, events, and mailing. Floating records in these files can also be deleted. A test can be used to check in advance whether there are any floating records.