>Nadya,
>
>Provided tLast_Updated_Date and cLast_Updated_User do not allow null values (and you do not recycle deleted records) then oldval('tLast_Updated_Date') will yield null for an insert, not null for an update
>
>If they do allow null values, you may have to use the table again and do a seek() in the table_again_alias.
>
>if( set('datasession') > 1 ) you can assume you are in a forms private datasession, so you do not have to close the table_again_alias
>
>Don't know the framework but I would update those fields for an insert if I were you

Gregory,

Thanks a lot for all your messages, they are extremely helpful. I guess, we can work it out. When I was talking about Stonefield I meant, that we need to do our changes in tables structure through Stonefield interface. I'm not sure, if it allows multiple changes at once. BTW, these two fields do allow NULLs.

For inserts we have two other fields: tEntered_Date and cEntered_User with default values for these fields. So, if it's an insert, these two fields get populated, otherwise two other fields.