The grid is refreshed any time the "AcceptChanges" method is called on the table to which the grid is bound.  This means that any time the grid has been modified (e.g. moving a row to another position, or sorting), then the grid is completely reset as if the grid was treated like ugrid.datasource=nothing and then ugrid.datasource = DT

I have been working with the Infragistics support folks, and while they are very nice, the feedback to this issue is that the ultra grid is "designed" to reset *anytime* there is a rowstate change in the datasource.  This seems pretty stupid and I believe older versions of the grid control did not have this problem (I am still trying to find an older system to test, but I have older code that would not have been released to our customer base if it had always acted like this).  So basically, what I have been told is that by simply changing the row state of a datasource, then be prepared to redo all of your grid settings as if you were first initializing the grid.

Other 3rd party controls do not have such design issues.  And since this is actually a follow-up to #369642, it begs the question, why wouldnt the forum engineers have just suggested to have the datasource change rowstate and that would reset everything in any ordered list? 

UGGGH.... I am posting this to publicly verify what I have been told and if this is true, then to let other developers be aware of the bound grid problems.  So Infragistics engineers... what is your public decision?  Is your grid so badly designed that changes in datasource row states reset your grid or is there a bug that needs to be fixed?

I look forward to the feedback!