I have a grid bound to a binding source which is bound to a es object. I can add and delete new records but if I edit a new record and cancel the edit with a

_bindingSource.CancelEdit

Kind of. I really didn't want to save the work to the database till the user was all done. But give them the ability to edit records they have been adding to the collection/grid. This is a project that I'm moving from dOOdads to es and adding data bindings. Under the old way I just did all my work in memory then save to the database when I was all done so I only had 2 calls to the database, 1 to load if they were editing a save batch and another to save when they were done. If I have to save every record the user is adding that could be up to 50 calls to the database by one user, with a user base of about 5 that could be about 250 calls to the database for saves alone during data entry. If this is the only way to solve the ability edit a record newly added record with the ability to "cancel" a edit and roll back to what was first entered then I just might have to lose that ability.

Any idea's? Or am I just doing this all wrong?

I too am trying to do something similar to this.  Basically, I have a set of child records for an employee - lets call them jobs which are bound to a datasource which is bound to a datagridview.  If I create a new row, and call EndEdit() on that row, but then I re-edit that row and call Cancel(), shouldn't it go back to the state when EndEdit() was last called regardless of what's in the db?