Then the other options posted here are better for you.
>I do use classes. I have a SAVEIT() method that is called when the SAVE button is clicked.
>
>I do not have abeforesave() or aftersave() method. It is local FoxPro tables.
>
>>I would do this in the save method of your control or form. Do you use classes? Is there a parent class? Do you have a beforesave() and aftersave() or something similar? Is each field saved as the user moves through a field or is there a save button? Is it local tables or sqlserver backend? Store the current value using a property of the control and then check it when the control loses focuses against the current value (or right after your save, etc) or check each field against it original value right after a save (if done using a button, etc)...
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
