Thanks for the response. However, I do believe that this is an issue. You should be able to hide these unnecessary nodes levels. As is, this does not allow full control over the tree structure.I will submit a feature request for this.

As I have to put up with these nodes, where do I set the node text?

Hi Mike, it seems that I was able to resolve this issue by replacing the control with a fresh one. I wonder if the issue occurred because I copied the control off an old from that was originally created using VS2003, upgraded to 2005 and then again to 2008!

I've had a few similarly odd issues pop up

Hi Mike,

It turns out that there is more to this that I first thought. I have now reproduced small example that also has this issue. I have no idea what's causing it. It seems intermittent

The dataset is the same as the one I was using when things were ok so it can't be the data source. The app simply loads the saved version of the dataset.

https://www.smartdata.co.uk/downloads/test_bind.zip

I'm not sure if this is related but it would seem that the leaf nodes (where their parent column is not null) are also being displayed as root level nodes. i.e. project with name 'Level 2A'  has parent 210.

Surely the control decides which rows will be root by the presence of null for the parent column as defined in the data table's relation.

What do I have to do to get the error? I ran your sample half a dozen times with no exceptions.

aim123 said:

Surely the control decides which rows will be root by the presence of null for the parent column as defined in the data table's relation.

The control displays the data you give it to display. If the root-level band of your data set is a table that contain all the rows, then all the rows will show up in the tree.

So you can use InitializeDataNode to hide the root-level nodes that have parent IDs.

Or, you could set up your data source with 2 tables. The root-level table would be a query that only returns the parent rows and then that table would have a Relationship to the child table (which contains all the rows) which then has a relationship back to itself.

The error occurs when you expand nodes. On the first expansion you see duplicates, on the second expansion you get the error. It doesn't matter which node, just choose any root node.

With regards to hiding nodes etc. in the InitialiseDataNode function I find this to be very, very slow. e.g I wanted to hide some colums for all but the root and leaf level nodes so I placed the following code in the initializeDataNode event..

If e.Node.Parent Is Nothing Or e.Node.Nodes.Count = 0 Then
          e.Node.Cells("ExpectedDuration_Hours").Column.Visible = True
          e.Node.Cells("ExpectedDuration_Mins").Column.Visible = True
        Else
          e.Node.Cells("ExpectedDuration_Hours").Column.Visible = False
          e.Node.Cells("ExpectedDuration_Mins").Column.Visible = False
        End If

This is simple yet takes 2 or 3  minutes to complete with the same dataset used in the test app!

I have used 'BeginUpdate' and 'SuspendLayout' but this makes no difference to performance.

Updated controls to version 9.1.20091.2050 - Issue appears to be sorted now!

Thanks for taking the time to look into this Mike!

No, what you have described I would expect. I know that I'm setting the text the same for the different band types. It was simply the case that this example caused the error. On my version I get 4 sub-nodes when I would expect only 2. Expanding another node would generate the error.
   
I'm using v9.1.20091.2012 of the UltraWinTree control. This issue definitely does occur with this version. Which version are you using?

With regards to the performance issue, I digress, this is simply another issue I encountered. I will try your suggestion to use ColumnSetGenerated.