Actually on further use, I did the following to reproduce behaviour.
I have a form with several related datagridviews and I have several
datasources that I can pick from. All this is bound.
I noticed that I had added a datagrid view using a wrong dataset that was
containing the good table but it was not pointing to the child table of the
master dataset so that I could get automatic correct relations between the
master and child datagridview.
I removed the wrong datagridview from the form, removed the objects
automatically inserted for databinding to that datagridview and the dragged
the correctly related datatable from my datasources to the form.
This action caused all the other datagridviews on the page to have their
columns reordered.
That, by my definition is aberrant behaviour and I call it a bug.
Microsoft, please fix that. Its a pain.
Bob
"Bob" <bd*****@sgiims .com> wrote in message
news:%2******** *******@TK2MSFT NGP15.phx.gbl.. .
During a form's development I noticed that when I changed bound dataset
defintions with the dataset designer (for instance adding a column to
one), when I come back and look at the form the ordering of the columns in
the datagridviews has changed. The column order that I designed is totally
different from what I had set using the datagridview column editor.
As far as I'm concerned this is a bug that should be addressed real quick.
its a pain having to reconfigure your column order on every data grid
every time you modify a dataset definition.
Bob
