Deleted duplicate post ......

I had a prepared answer, all written out before I even submitted the question to the Quiz, in case no one got it, but Docker did. He came up with the exact reason as to why this happens (rows sometimes remaining in a Proposed version). Pradeep was close...

Hmmm ... well, I guess more clarification is necessary. I am **not** referring to the actual process in your DataAccess class of saving to the database. Whatever methodology you currently use to access the database (be it TableAdapters or DataAdapte...

There is something you're overlooking and it has to do with the version of the changed rows. That's the only "hint" I'm giving for now. ;0)...

This is not all that complicated. I'm quite surprised that no one has tried to answer it yet! But, I'm not ready to give away the answer just yet .... please, doesn't anyone want to take a stab at this?...

What problems can arise when attempting to save changes back to the database, when using Parent/Child DataRelations ......