Simple enough. Works great. Thanks

Hi,

One thing you could try is handling BeforeRowDeactivate. You could check IsAddRow and if it's true, call CancelUpdate on the row.

Yes, by saving I mean commiting the data to the db.

This is how I would like the grid to behave:

• Pressing Return/Enter should fire BeforeRowUpdate. This is what happends by default so this is fine.
• Moving away from the row by any means will cancel the add row and clear it. (One exception may be when tabing from the last cell on the add row which might behave same as pressing return but that doesn't concern me.)

When row.IsAddRow == false

• Pressing Return/Enter should fire BeforeRowUpdate. This does not happen by default and it requires adding a key mapping to the grid.
• Moving away from the row by any means should fire BeforeRowUpdate. Happens by default. 

So the only issue really is how to prevent the AddRow from being commited when the user does not press Return/Enter or tabs out of the row. The problem is that in BeforeRowUpdate for the AddRow I don't know if the user is moving away from the row or has pressed Enter.

Thanks

I don't understand... What exactly do you mean by "I try to save the row in the BeforeRowUpdate". What exactly are you saving? You don't have to manually write the grid data to the data source, the grid will do this automatically. Do you mean you are writing the data to the back end?

BeforeRowUpdate should still fire, whether the row is a new row or an existing row. You can check row.IsAddRow to see which one it is.