>Jim,
>
> This is not a rule or trigger. The stored procedure is get_new_index() which is the default value. The command, INSERT INTO, does not wait to see if there is a default value, it just leaves any field not specified in the memvar list, empty. This immediately violates the uniqness of the value of that field. However, after the error is issued, the empty field is relaced by the default value. Maybe the error message is wrong. I don't know how this could happen.
>
Eric,

Check the data in your table, I'll bet there is a record in there with a blank ID field. Just delete that record and pack and you should have no more problems. The blank ID field should only be temporary until the default value is placed on the record. The only way you get the error is if there is already another record that has a blank ID.