> However, I'm really puzzled about why you want to do things this way.

Keys

> should not be editable. An "edit" that changes the key and sets all other
> columns to default values isn't an edit - it's an insert. If you want a
> new row to replace an existing row, have a sequence that inserts the new
> row and deletes the one with the old key. That way, DefaultValues kick in
> automatically, as designed, and the whole process is squeaky clean.
>

Hi Helen,

Sorry, my mistake. Yes, it actually is an insert. The user enters an ID
number, which is the key field, then enters the values for all the other 20
fields or so, for that particular ID number. My concern is that after the
user has already entered values for some of the fields then he/she decides
to change the ID number, I would like all the other fields to reset to their
default values, which is 0, and the user can then start anew.

So do I have to write my own code then? I was actually putting it off in
case there is a better way :)

Thanks,
Jane