# Orphan record check

This window is displayed by clicking on the Orphan record check option in the Files menu

It is used to tidy up problems with data tables that can not be fixed directly by manual editing.

In many cases we use header and child tables, eg Manifests have a header table to define the manifest number, source destination etc. and then a child table for the items in the manifest list.

The child records are displayed only when the header is selected. If the header is missing you can not access the child records, eg to delete them.

Also sometimes records are created wil null values in key fields, which also make it difficult to delete them.

This form is modal. You must close it before you can access other forms or the menu

1. Select the options to apply

a. Checking for orphan details records – these usually need to be deleted.

b. Checking for headers with no child records – these may be OK but often can be deleted.

c. Checking for nulls – usually need to be deleted.

2. Select the tables to be processed

3. You can check or uncheck all of the tables using the buttons.

4. The report button, will perform the check but not actually change ant\y data. Usually you would run this to determine if there are any errors.

5. This option will create dummy headers with the corresponding key values (Manifest number etc) so that the orphan records can be displayed and deleted. Then the dummy header can be deleted.

6. This option will delete records with null values in key fields.

Document OrphanCheck.htm