Calloway | Builds boring website stuff for opinionated developers | Web Site library

A simple WinForms app to learn about control data binding. Code below from a Form named frmMain and containing TextBoxes txtFirstName and txtLastName, and a numeric up/down named nudRow. Editing the text in the text boxes and changing the row, I notice the previous DataRow has values changed in the 'proposed' row version (eg _Tbl.Rows[3][1, DataRowVersion.Proposed]), but the RowState is still 'Unchanged'. What am I missing that would make 'proposed' become 'current' and change the RowState? The commented out 'DataSourceUpdateMode' didn't make any difference.

I'm also pretty fuzzy on why I need to keep resetting the TextBox DataBindings instead of just setting the DataRowView (_CurRow) in the numeric up/down value changed event.

EDIT: I thought I was pretty clear that my question was: Why didn't the RowState change? Additionally, is there a standard pattern (validation or something) typically used to process the 'proposed' value and change the RowState? As an aside, I was wondering why I had to rebuild the data binding instead of just changing the value of the thing that's already bound, but maybe that needs to be a separate question.

EDIT2: After looking at some documentation on DataRowVersion.Proposed, it looks like I should add code something like below to my numeric up/down value changed event. Unfortunately, I can't answer my own question while the post is on hold...