aim123 said:

With regards to the code sample, I reiterate that this project uses pivoted data built from 3 separate datasets... columns, rows and values. The example provided uses the column data set and so each row actually represents a column. It is equivalent to looping through the columns on the pivoted dataset.

 Ooh, I see. That makes sense, then.

Hi Mike,

The issue is that the binding manager is re-ordering the columns. I have checked the pivoted dataset and the column order is correct. Hence the requirement to re-order. I would suggest that there is something unknown about the binding manager as I am relying on default behaviour.

With regards to the code sample, I reiterate that this project uses pivoted data built from 3 separate datasets... columns, rows and values. The example provided uses the column data set and so each row actually represents a column. It is equivalent to looping through the columns on the pivoted dataset.

Well, what would you suggest? The grid shows the columns in the order that the BindingManager returns them. There's no other order the grid can use, since that's all it has access to.

Anyway, the code you have here is horribly inefficient. Why are you looping through every row in the data table? You are essentially setting the VisiblePosition repeatedly to the same value for every row of data. You only have to do this once and you should do it in the InitializeLayout event.

Yes thanks fixed with the following but I don't feel that this hould be required.

      Private Sub setColumnOrder()

      'Loop through all the columns and set
      Dim IntOrder As Integer = 0
      For Each row As DataRow In DsColumnsByTestTypeIDForResultsForm1.Tables(0).Rows
       Me.UGResults.DisplayLayout.Bands(0).Columns(row.Item("Name")).Header.VisiblePosition = IntOrder
        IntOrder += 1
      Next row
    End Sub