very strange behaviour
-
I'll try to explain this. I have a Windows form with a datagrid. The datagrid binding has been set as MyDataGrid.SetDataBinding(MyDataView, "") The dataview has also a RowFilter to show only some records. Now, the problem is that I need to do some calculations whenever something is changed in that table. For that I use the RowChanged and RowDeleted events. Now, I have no problems with rows deleted, or rows that are modified, but I do with rows added. When I add a new row, the RowChanged event does fire, and checking the row property of the event argument I can verify all the data in that row is correct. However, a that point, all the dataset methods don't seem to "see" that row. Very strange because the row is being showed on the datagrid. More strange, if I make any other change, the row becomes "available". It was driving me crazy because a Select method executed on the datatable would not return the newly added row, but it would if other change was made subsequently. Just to be sure, in the RowChangedEvent I saved the dataset at that stage using the WriteXml method, then I looked at it and it did not include the new row. But if I check the count property of the datatable, it has increased by one. so :doh: it seems that by the time the RowChangedEvent is fired, the row is not available to the dataset methods even though the row IS available to the dataview :wtf: to make things even weirder. I have some code that checks for data integrity in the RowChanged event, if the data is wrong is display a message box and then calls the RejectChanges() method of the row. That in turn triggers the event again and it exits the procedure because the row is null. Now if that happens (meaning, if I enter wrong data to trigger the rollback) all subsequent insertions work fine. even weirder, if I exclude the event handler before calling RejectChanges() (so the RowChanged event won't be trigger by the rollback) the problem persists, meaning new rows are not "seen". this does not make any sense to me, and only happens if I do my calculations from the RowChanged event. If I add a button and use the button's click event it's fine, so it looks that when the RowChanged event is fired, the new row is in a sort of intermediate state (not the added state but some unforseen state). This looks like a bug, but I really have no clue what's going on. I hope this is understandable, it's so weird that I can't make any sense of it.
-
I'll try to explain this. I have a Windows form with a datagrid. The datagrid binding has been set as MyDataGrid.SetDataBinding(MyDataView, "") The dataview has also a RowFilter to show only some records. Now, the problem is that I need to do some calculations whenever something is changed in that table. For that I use the RowChanged and RowDeleted events. Now, I have no problems with rows deleted, or rows that are modified, but I do with rows added. When I add a new row, the RowChanged event does fire, and checking the row property of the event argument I can verify all the data in that row is correct. However, a that point, all the dataset methods don't seem to "see" that row. Very strange because the row is being showed on the datagrid. More strange, if I make any other change, the row becomes "available". It was driving me crazy because a Select method executed on the datatable would not return the newly added row, but it would if other change was made subsequently. Just to be sure, in the RowChangedEvent I saved the dataset at that stage using the WriteXml method, then I looked at it and it did not include the new row. But if I check the count property of the datatable, it has increased by one. so :doh: it seems that by the time the RowChangedEvent is fired, the row is not available to the dataset methods even though the row IS available to the dataview :wtf: to make things even weirder. I have some code that checks for data integrity in the RowChanged event, if the data is wrong is display a message box and then calls the RejectChanges() method of the row. That in turn triggers the event again and it exits the procedure because the row is null. Now if that happens (meaning, if I enter wrong data to trigger the rollback) all subsequent insertions work fine. even weirder, if I exclude the event handler before calling RejectChanges() (so the RowChanged event won't be trigger by the rollback) the problem persists, meaning new rows are not "seen". this does not make any sense to me, and only happens if I do my calculations from the RowChanged event. If I add a button and use the button's click event it's fine, so it looks that when the RowChanged event is fired, the new row is in a sort of intermediate state (not the added state but some unforseen state). This looks like a bug, but I really have no clue what's going on. I hope this is understandable, it's so weird that I can't make any sense of it.
:doh: Sreejith Nair [ My Articles ]