Hi Abhishek,

So there has to be some factor in your real app that is different from the sample. I would try a process of elimination. Take a look at the events of the grid you are handling. Comment out the code in those events and see if the problem still occurs. Or put a breakpoint in each of the events and then reproduce the issue so you can see which of those events is firing and that might give you a hint which code is causing the issue.

Another approach you could take is to make a copy of your real app and try to reduce it down to the simplest possible app that still reproduces the issue. If you can narrow it down to something we could run, then we could look into it further. But without being able to reproduce the issue, there's no much more we can do.

Hi Mike

The sample behaved very well on my machine as well. We tried with a number of variations on your project, and in each case the grid is behaving exactly as it should.

Basically we are using dataview to bind the grid and the rowfilter was being used. The phenomenon happens when UpdateData is called before setting the values in the row which would satisfy the rowfilter. Looking from the grid's perspective, I think this is how it should be.

Many thanks for the help!

Best Regards

Abhishek

Hi Abhishek,

I can't see any obvious reason why you would get those results. So I tried this out in a simple test project to see if I get the same behavior and I don't. I am attaching my test project here, but the results I get are like so:

row = Me.UltraGrid1.DisplayLayout.Bands(0).AddNew()

ListObject: System.Data.DataRowView
IsTemplateAddRow: False
IsUnmodifiedTemplateAddRow: False
IsAddRow: True

Me.UltraGrid1.UpdateData()

ListObject: System.Data.DataRowView
IsTemplateAddRow: False
IsUnmodifiedTemplateAddRow: False
IsAddRow: False

The row has a ListObject in both cases, just as I would expect. I am attaching my simple sample project here so you can try it out on your machine. If you get the same results as I do with my sample, then something else is happening in your real application which is causing the behavior. In that case, I would look at the events of the grid that you are handling and see if maybe some code in one of those events is the cause of the issue.

If my sample behaves the same way as your actual application on your machine, then that means you must be using a different version of the assemblies and maybe this is a bug in the version you have.

Hi Mike

I am reproducing below the contents of the immediate window executed after the following statement:

gRow = myGrid.DisplayLayout.Bands(0).AddNew()

?gRow.ListObject
{System.Data.DataRowView}
    System.Data.DataRowView: {System.Data.DataRowView}
?gRow.IsTemplateAddRow
False
?gRow.IsUnmodifiedTemplateAddRow
False
myGrid.UpdateData
?gRow.ListObject
Nothing
?gRow.IsTemplateAddRow
False
?gRow.IsUnmodifiedTemplateAddRow
False

First three statements are before calling UpdateData, next UpdateData is called and the same three statements are executed again.

Kindly Advise.

Best Regards

Abhishek

Hi Abhishek,

That's really weird. My best guess is that the row you have a reference to is not the new row. What must be happening is that when you commit the row (by calling UpdateData), the row you referenced becomes the new TemplateAddRow, and the real row that got added to the grid is a different row.

You could confirm this by checking:

gRow.IsTemplateAddRow and gRow.IsUnmodifiedTemplateAddRow

If either return true, then that would support my theory.

In theory, th "real new row should be the last row in the rows collection. So after you call UpdateData, you could re-get the row like this:

gRow = oGrid.Rows(oGrid.Rows.Count -1)

Now... I'm not sure if the TemplateAddRow counts against the row count. And it may also depend on whether that row is Fixed or not. So you might have to use -2 there instead of -1.