Hi Matthew,
The datagrid in asp.net and the datagrid in windows.forms really have
nothing in common so it's wise not to try to force one to act like the
other.
The datagrid (windows.forms) binds to objects that implement IList or
IListSource.
Fortunately CollectionBase implements the IList interface, but you still
need to pad out Add and Item.
Once that's done you should be able to see your data as long as you add the
objects to your collection before you bind the collection to your database.
If you want the grid to be sortable, searchable, notifiable and
addnewable(?) you'll need to implement the IBindingList interface, which is
a bit more complex but there are a couple of post in the past few weeks that
collectively probably have a complete solution.
You might also want to look at IEditableObject for your 'customer' objects
but you don't need it.
The datagrid in asp.net and the datagrid in windows.forms really have
nothing in common so it's wise not to try to force one to act like the
other.
The datagrid (windows.forms) binds to objects that implement IList or
IListSource.
Fortunately CollectionBase implements the IList interface, but you still
need to pad out Add and Item.
Once that's done you should be able to see your data as long as you add the
objects to your collection before you bind the collection to your database.
If you want the grid to be sortable, searchable, notifiable and
addnewable(?) you'll need to implement the IBindingList interface, which is
a bit more complex but there are a couple of post in the past few weeks that
collectively probably have a complete solution.
You might also want to look at IEditableObject for your 'customer' objects
but you don't need it.
Hope that helps, it's not so bad once you get used to it.... ;-)
J.
Jasmine
www.datagridcolumnstyles.net
Custom DataGridColumnStyles for the Microsoft .Net Windows Forms DataGrid
"Matthew" <matthewt...@hotmail.com> wrote in message
