Hi tejuguasu,

Welcome to Visual WebGui

I don't have Oracle to test, but using just normal ADO.NET DataTable and assigning it to the DataSource of my DataGridView, changing some of the Columns DisplayIndex and Visible properties works fine in my testing in the upcoming Visual WebGui Release d, as well as the released version 6.4.0 Release c.

I am therefore unable to reproduce this problem. If you still have the problem, please create the most minimal reproducing sample application, clean it, zip it and then email it to the support email address (see my signature) along with the full Http reference to this thread. Please also post here when you have sent it.

As for the sample code, plesae either base it on memory based ADO.NET, or use Northwind MSSQL sample database, so we will be able to test your application.

Palli

Hi tejuguasu,

You are welcome

You do have some good hins as this is only happening to two tables. Some things that might be interesting to look for is if the AutoGenerateColumns property is true or false, and if it is false, you should view the designer generated code for the columns added to see if there could possibly be any duplicate column declarations in the code. We had some problems with earlier designers that under certain scenarios would create duplicates of the controls and add those duplicates to the form, leaving the original (and the one you are setting properties for) orphans.

Should this be the case, you would for example have DataGridView1 as the control you are using in your code, but looking at the designer generated code, you would have DataGridView1 created as an instance, but not added to the form, then you would have a new duplicate, DataGridView2, and that one would be added to the form's Controls collection. When you set some properties for DataGridView1, that would have no effect, as only DataGridView2 is actually on the runtime form.

This could be something to look for at least, although it may not explain or account for the problem.

Palli