Kevin,

There is apparently a bug in the framework detecting a state change if the change is made to a table other than the default table. I have found a way around my immediate problem but I wanted to pass this along, since I keep bumping into it. I suppose I'm using these tables in a way other than you intended. In my defense, you and Josh are the ones who got me started using them this way.

All you need to do to recreate the problem is to test the row state after changing a column value (in this instance, I was using the event CheckedChanged() on a check box and didn't want to invoke any code if the change was just due to moving to a new row. I did double-check to make sure that I did have the BindingSource and BindingSourceMember set correctly.

Thanks.

Linda