>...snip ... You can do this from the validation rule though...
>>
>>Make the table's record validation rule
>>
>>TimeStamp()
>>
>>and make a stored procedure in the dbc:
>>
>>PROC TimeStamp
>>REPLACE tbl_lstChange WITH DATETIME()
>>RETURN .T.
>>ENDPROC
>
>Hi Erik
>
>I've got the equivalent in the code behind my save button. My tables are never browsed and it means I don't have to have enter a validation rule for every table. However I'm sure you've considered these issues --- so is it cleaner etc to do it through the database?

I do it through the database because most of my tables aren't protected from users in a browse (I have a lot of power user clients). Having this code in the dbc ensures that it always gets updated, but also that I don't have to do it behind every save button, and everytime I am about to TABLEUPDATE from a view.