Question RE: AcceptChanges method

[Slow_Learner]

If I have an event handler for the DataTable.RowChanged event, and I change some data successfully, and then invoke AcceptChanges for that row, why does RowChanged fire two times? And if I invoke .AcceptChanges again right away for the same row, why does RowChanged fire again? Didn't I accept the changes for that row already, making the RowStatus Unchanged?

ms-help://MS.VSCC/MS.MSDNVS/cpref/html/frlrfsystemdatadatarowclassacceptchangestopic.htm
ms-help://MS.VSCC/MS.MSDNVS/cpref/html/frlrfsystemdatadatarowclassrowstatetopic.htm

Edit: Uh, after stepping through this process in the debugger I see that the RowChanged event has nothing to do with RowState - which makes me wonder how you properly set an event handler for a table to watch for changing data and not have it fire multiple times per change?

[Slow_Learner]

Well poop on .RowChanged anyhow, the .ColumnChanged event does just as well for my purposes and doesn't fire twice when you .AcceptChanges.

Edit: Err - I'm not sure if this makes any sense, apparently the .RowChanged action fires for both the DataRowAction.Change and DataRowAction.Commit actions ... but DataRowAction.Change does not occur until you .Commit! What the hell?

I mean, you can examine the event args as in:
If e.Action = DataRowAction.Change Then
...
End If

But what were they thinking? I don't get it.