C cellvalidating

When this event is canceled in data-bound mode, the new value is not pushed to the underlying data source.When this event is canceled in virtual mode, the Cell Value Pushed event will not be raised.However, the user may prefer to validate all the data cells in a row at once.

In this situation the editor is not kept active when the validation fails and pressing the Esc key does not revert the changes as the editor is already closed.

On the other hand, the Cell Value Changed event seems to trigger only when the value of the cell changes, which means the validation code runs only when the value changes and not everytime a user changes cells.

Now, since so many books use the Cell Validating event, I wonder if there is not any gotcha (in display for example) with using the Cell Value Changed?

I understand that the impact in performance should be irrelevant when using simple validation and conditional highlighting rules but I would as much prefer it not to run useless code everytime the user moves to another cell if it can be avoided.

Thanks, Depends on what design pattern (if any) you are following.