How can I ensure that my ISAM files match the Runtime entries?

The Runtime database structure has two layers: the LINC Developer layer and the D-ISAM layer. It's possible that data deleted in the LINC Developer layer can still be present in the D-ISAM data files. The LINC Developer layer is controlled by the LINC Developer MAINT flag. The Easysoft ODBC-LINC Developer Driver's Physical deletion option gives you control over the ISAM layer. The option purges any records in the ISAM layer that have been physically deleted in the LINC Developer layer of the database. Physical deletion should only be used when initially accessing the data source. It can be a potentially dangerous option as it permanently deletes records from the ISAM files. We recommend that you use Physical deletion once to bring the layers into line on first usage.

Be aware that this option can permanently erase data.