parent/child bindingsource save new fails
-
Parent = context.table child = From t in parent where ... In properties, the datasource is set to parent as well. The bindingnavigators.bindingsource are set to child, all controls and datagrids are bound to the child bindingsoure. Add new will instaniate a new row. It displays in the datagrids; however, it will not save. The primary key field maintains 0. As soon as I sort or call a new query the row is gone. On reload the row is gone. Is there a problem with a child binding source? me.validate() me.parentsource.endedit() me.child.endedit() parent.resetcurrentitem() me.context.submitchanges() I have tried ending edit in reverse order and not reseting the current item (needed to update the changes, which works correctly for some strange crazy reason). The problem exists solely with saving a new row. Does it make a difference that there are two binding navigators? Due to space and design, I opted for 2, but I have tried the addnew on the second. Hmmm ... Ideas? :^)
-
Parent = context.table child = From t in parent where ... In properties, the datasource is set to parent as well. The bindingnavigators.bindingsource are set to child, all controls and datagrids are bound to the child bindingsoure. Add new will instaniate a new row. It displays in the datagrids; however, it will not save. The primary key field maintains 0. As soon as I sort or call a new query the row is gone. On reload the row is gone. Is there a problem with a child binding source? me.validate() me.parentsource.endedit() me.child.endedit() parent.resetcurrentitem() me.context.submitchanges() I have tried ending edit in reverse order and not reseting the current item (needed to update the changes, which works correctly for some strange crazy reason). The problem exists solely with saving a new row. Does it make a difference that there are two binding navigators? Due to space and design, I opted for 2, but I have tried the addnew on the second. Hmmm ... Ideas? :^)
PrissySC wrote:
I have tried ending edit in reverse order and not reseting the current item (needed to update the changes, which works correctly for some strange crazy reason). The problem exists solely with saving a new row.
..when there's no parent to link the children to. Save the parent first, without any children.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] They hate us for our freedom![^]
-
PrissySC wrote:
I have tried ending edit in reverse order and not reseting the current item (needed to update the changes, which works correctly for some strange crazy reason). The problem exists solely with saving a new row.
..when there's no parent to link the children to. Save the parent first, without any children.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] They hate us for our freedom![^]
After fighting with this and reading your comment ... I finally figured out the connection with the new to the relationship of the parent. It was not the actual save for the context that caused the problem, but rather how I was initiating the "new". parent.add(child.add) solved the problem. Now, when saving the changes to the context, no error and I get validation. Off to fight with excel export ... :~ Thanks for your comment!