I just discovered that  XDG.RecordUpdateCanceling/ed in fact won't work either, because the dirty record is still in the BindingList when the event is fired.  I must check for any other dirty items before clearing the dirty data flag, and the dirty AddRecord I'm "cancelling" is still there in this event.

In case I've obscured my intent, I want to clear a dirty data flag after cancelling an edit for an add or update, when there are not other dirty items (hence the problem above for the AddRecord that is not yet cleared when for  XDG.RecordUpdateCanceling/ed).

Does the list you're using implement ICancelAddNew (e.g. BindingList<T> does)? If so then that is being called when the add new is cancelled so maybe you can use that (e.g. CancelNew on the BindingList<T> is virtual so you might be able to override it and do what you need there).

Thanks for the heads-up on that; didn't know it.  But yes, I was deriving from BindingList<T>.  Interesting thing though, my dirty add record is still in the list when this CancelNew is called (just as with XDG.UpdateCancelled).  So I'll putting some code in overridden BindlingList<T>.RemoveItem next.  It's definitely out of the list there.

The item is removed in that method so perhaps just get the item before calling the base, call the base (so it gets removed) and then do your clean up before returning from that method.

You're absolutely right.  I'm in crunch mode now and I was posting to you guys as I worked this one out.  I'm using a composite pattern with hierarchical viewmodels, and there's alot going on.

Are you a developer Andrew?

Yes