Mike,
All of my data entry tables are buffered - that's part of my basic design tenets. I use TableUpdate() or TableRevert() to Save/Cancel any changes. I prefer to use the InteractiveChange method rather than Valid because it IS affected with any change even if the user re-enters the data as it was. If they truly don't want to make a change then TableRevert() discards the buffered changes, including the updated timestamp. Otherwise I REALLY want to know if someone has been fooling around with the data. In every app where I have implemented this I also store a user code for security reasons. This is a matter to decide with the end users and whoever manages data security for the app.

>Hi Barbara,
>Thanks! I will do this, Do you just do a REPLACE then? I think (to build on to your method) I will add it to my VALID instead of INTERACTIVE CHANGE, just because if the value is changed, but you change it back without leaving the field, your record will show it was changed but actually wouldn't have. Does this sound like a good idea?