>We have the similar code in our classes, but I realized, it is not sufficient, since it doesn't check for buffered changes.
Nadya,
If you do a seek() or COUNT in the same table (i.e., without re-opening it), you run the risk of getting error messages, caused by the fact that validation is carried out before you actually want to save the record.
The philosophy I apply is to check for changes only when the user tries to save changes. This has several advantages, specifically, you wouldn't need to worry about buffered changes.
However, I realize that if you want to check for changes earlier this solution may not be perfect.
Regards, Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
