>We haven't been able to narrow down the exact test case, but here's what is happening:
>
>We have an INSERT - SQL statement where a field/value list is specified. There are a couple of fields that aren't in the field list of the command that are being populated with values from the previous record even though the fields themselves have a zero as their default value.
>
>Example:
>

INSERT INTO MyTable (f1, f2, f3) VALUES (1, 2, 3)

>
>Fields f4 and f5 are being populated with values from MyTable's prior record instead of defaulting to zero.
>
>Does anyone know of any circumstances that could make this happen?

Set carry off