>>Erik, WorkLog in File Section already done that for you!
>>It handle all possible cases editing the table!
>>- Append Blank, then fill in and Update
>>- Delete Record
>>- Recall Record (also make the delete mark switch but trigger Insert Trigger!)
>>- Insert-SQL
>>- Update Old Record
>>
>
>Thanks, Justok. The reason I need a timestamp is not really for audit trail purposes, but like I said, synchronization purposes. Since I haven't found a way to update the timestamp on the dbc, level, I have already implemented a simple version of what I think our worklog program does. My robots then use this generated table to manually change the timestamps and then its business as usual. Thanks again for the suggestion though.

Not at all, As you said, there should a request on wish list!
each record should have a datatime field to handle any Add/change/delete!

Why? This is mainly for Real world situation!
For example, a normal production company have many new item put into the system
and some item maybe produced for long time and no customer make orders...

Then, a datetime field can check whether the rubbish record can be deleted or archieve to another table....
My boss make a rule for me:

if item Not call for order in 18 months, move those records into Olditem table
if Olditem Not call for order in 36 months, erase those records!
if Olditem record really call for order, move backwardly to item table!

Then, it will make the SQL search time quick a lot as most rubbish records are skip!

Now, I need much coding and time to handle the above request... :~~~~