>Very hard to suggest anything, since it's definitely not normal behavior. Perhaps as suggested by Tore just to prevent bad data (not really a good solution, since we don't know the cause) is to specify all fields in Insert with their default values.

Understood. We actually came up with another work around.

If we skip beyond the table's last record (i.e. EOF) and then do the insert, then the problem does not seem to occur anymore.