DataGridView Problem

DataGridView Problem

• chuckcycles

  I've encounter the same problem with the DataGridView.  In my case I bind to a List like this:
  
  // original populated list
  List<Decimal>^ frequencies = gcnew List();
  frequencies->Add( Decimal(1.0) );
  frequencies->Add( Decimal(2.0) );
  
  BindingList^ bl = gcnew BindingList<Decimal>( frequencies );
  BindingSource^ bs = gcnew BindingSource();
  bs->DataSource = bl;
  frequencyGridView->DataSource = bs;
  
  When the grid appears it has two blank rows.  If I change the number of values in the original list all that happens is I see more or less blanks rows.  I never see the data in the cells although if I debug I can see that values are there.
  
  It would be nice to get a fix to this soon.
  
  Michael
  
  

• Chelten

  Hi Mark,
  
  Thanks for replying.
  
  I did always have the .AutoGenerateColumns set to false immediately before the datasource binding, and in my source code, there is no other places where the datasource binding is called. 
  
  But it still does not work. 
  
  I traced the source code and have two break points: one in the rowsadded() event and one in the CellValidating() event.  It appears to me that immediatly after the datasource binding occurs, the dataset is read into the datagridview (I have three records in the dataset, and the events were called three time each).  Within the two events code block, I can even see some data loaded in the cell.  But yet, the data is not displayed on the datagridview, only the headers are displayed with empty cells.
  
  DQ
  
  
  
  

• Tyagi

  I am convinced this is a bug...
  
  I create another Windows program.  This program has nothing but a form with a DataGridView which has pre-defined columns created using the VS IDE designer. 
  
  And I was unable to get the datagrid populated.  Again, if I set the AutoGenerateColumns to true, and then the grid is populated with data records.  Of-course the auto generated columns are appended following the predefined columns, even though the predefined set has exactly the same column names as the auto generated does.
  
  Can someone confirm that this is a bug
  
  Thanks
  
  DQ
  
  

• BBVB

  Hi,
  
  what do you mean exactly by "you'll have to use code to achieve this"
  
  Thanks
  

• multisession

  Regarding #1 - this is by design. We do not support modification of child collections in inherited forms/controls at design time.
  
  Regarding #2 - This is a behavior change that is subtle -- We now default AutoGenerateColums to true unless you databind the DataGridView at design time. So, you need to change your code to set AutoGenerateColumns to false before you set the datasource:
  
  

  dataGridView1.AutoGenerateColumns = false; dataGridView1.DataSource = bindingSource1;

  
  
  Hope this helps!
  -mark
  Program Manager
  This post is provided "as-is"
  

• Ghawas

  When I select an item in a combo box and the search button the first time, the code, "AutoGenerateColumn = false", it works. When I select another item from a combo box and hit the search button, the code is traced and executes the "AutoGenerateColumn = false" statement but when displaying the new datagridview with the new item, the datagridview seems to revert back to the default.

  I have written the code exactly how Mark Rideout (Microsoft) suggests.

  This is definately a bug in the framework.

  
  

• BenLovesSQL

  In this version of Visual Studio we do not support modifying properties of the DataGridView at design time for inherited forms and chose to disabled this scenario intentionally. This decision was not make lightly and we understand customers would like this functionality, but the existing visual inheritance architecture in combination with collection based controls makes it extremely costly to address.
  
  We hope to enable this in future versions. Until then, you'll have to use code to achieve this.
  
  Thanks,
  -mark
  DataGridView Program Manager
  Microsoft
  This post is provided "as-is"
  

• Mark Essien

  
  Hopefully, MS folks don't give up on this problem...
  
  How about everyone else   Do you run into the same problem with DataGridView like I do   Either a) noone is working on the DataGridView, b) noone has the problem that I have, which means I did something wrong, or c) you guys did run into the same problem, but are watching this thread with the same hope that we are going to get some good response from our friends at MS.
  
  I really need to solve this problem, because it stops my development.
  
  Can you please hep, MS
  
  Thanks.
  
  

• SGK

  Hi,
  As I mentioned it's a designer restriction, the nature of inheritance is not affected by this problem. You can use code in the constructor of your derived form to modify the properties of the inherited DataGridView. The compiler will do its best. But unfortunately the modification process is apparently more difficult since you can't see the result at design time; you'll have to build and run your project to see the results at run time.
  Anyway thank you Mark for your reply.< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

  
  
  

• pcsql

  David - Where do you add your columns to the DataGridView and when do you set the column's DataPropertyName value
  
  -mark
  DataGridView Program Manager
  Microsoft
  This post is provided "as-is"

  
  

• Christian Burgener

  Hi,
  I have a similar problem, it's even worse. I can't change any property of the DataGridView in the inherited form. The access modifier for the DataGridView is protected, I even set it to public, but the designer treats it as private and all the properties are readonly. I didn't have this problem in Beta 1.
  Can anyone help is there any solution other than to wait for the final version < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

  
  
  
• DataGridView Problem