J
JaedenRuiner
Guest
So,
DataGridView, assign a BindingSource as the DataSource. Now, during different operations the DataSource of the BindingSource is changed.
This will trigger the OnDataBindingComplete() method (overridden in descendant Grid class).
Howeve,r when I first started playing with it, this seemed the perfect solution.
Now, though, it appears that when the method is fired the "Rows.Count" is always 0. I continue past the break point out of this method and the DataGridView shows rows.
I need to be able to access DataGridView.Rows[0].DataBoundItem at run time, before the rows are rendered but after the underlying datasource has been changed.
How can I get this?
Thanks
Jaeden "Sifo Dyas" alRaec Ruiner
"Never Trust a computer. Your brain is smarter than any micro-chip."
PS - Dont mark answers on other peoples questions. There are such things as Vacations and Holidays which may reduce timely activity, and until the person asking the question can test your answer, it is not correct just because you think it is. Marking it correct for them often stops other people from even reading the question and possibly providing the real "correct" answer.
Continue reading...
DataGridView, assign a BindingSource as the DataSource. Now, during different operations the DataSource of the BindingSource is changed.
This will trigger the OnDataBindingComplete() method (overridden in descendant Grid class).
Howeve,r when I first started playing with it, this seemed the perfect solution.
Now, though, it appears that when the method is fired the "Rows.Count" is always 0. I continue past the break point out of this method and the DataGridView shows rows.
I need to be able to access DataGridView.Rows[0].DataBoundItem at run time, before the rows are rendered but after the underlying datasource has been changed.
How can I get this?
Thanks
Jaeden "Sifo Dyas" alRaec Ruiner
"Never Trust a computer. Your brain is smarter than any micro-chip."
PS - Dont mark answers on other peoples questions. There are such things as Vacations and Holidays which may reduce timely activity, and until the person asking the question can test your answer, it is not correct just because you think it is. Marking it correct for them often stops other people from even reading the question and possibly providing the real "correct" answer.
Continue reading...