It does the same thing unless I get the new index and don't use the default value trigger. I seems like you should be able to use this command on tables with default values specified.:-(

Eric

>INSERT INTO ... FROM MEMVAR *write* a blank value to each fields that do not have a matching variable. The default value trigger isn't fired when you supply *any* value to the field.
>
>You should use INSERT INTO MyTable (MyField1, ...) VALUES (MyVar1, ...) instead.
>
>HTH
>
>> 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.