>>Yes with CA and VFP8+. However possible with earlier too. Then where slightly differs:
>>
>>where oldval(myview.myTimeStamp) == curval(myView.myTimeStamp)
>>
>>Actually rethinking this where would be easier to construct this way for both the CA and w/o CA (just add both PK and timestamp as keyfields and mark at least timestamp as updatable).
>>Cetin
>
>In this case, where would you update the timestamp? Is it possible to do this in the table definition? (I think there will be some problems here.) Or does it have to be done at the form level?
>
>===
>
>In any case, it might be worthwhile to switch to VFP version 8 or 9, eventually. I am still using version 6 for now, but perhaps I can convince my client to switch.

Not in table definition but in a stored proc. For example I've SaveData() wrapping TableUpdate() - signature is same, SaveData([nRows [, lForce]] [, cTableAlias | nWorkArea]
[, cErrorArray]).
Cetin