I think the trigger fires with INSERT INTO but you have to be careful what you are inserting. If you are setting something like a unique primary key the INSERT INTO will err because INSERT INTO has already violated the uniqueness of the field, if, it is not specified in the VALUES list or a memvar. INSERT INTO puts a null value anywhere VALUES is not specified for a field. This why I continue to generate index keys with a global routine .vs a stored procedure.

>Hmm. I was thinking field defaults...sorry. But still, it'll fire on the _buffered_ table, I do believe.
>
>>Funny, they fire when I do insert into... what use would they be if they didn't?


Eric K.