Re: Data bound application infrastructure

relationships within the dataset will get this working for you,
you may need to pass a "BindingContext" around between your forms so as
currecnymanagers navigate through objects on one form, you see the same
changes on another form with the same BindingContext.  There should be
plenty of google examples of this.

If you want to get things like this working with custom objects instead of
the dataset/datatable classes, these interfaces would be a good starting
point.

ICollection
INotifyPropertyChanged
IEditableList <-- for in-place grid editing
IBindingList
ITypedList

IListSource

-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:[email protected]]On Behalf Of
Brady Kelly
Sent: Thursday, June 28, 2007 7:39 AM
To: [email protected]
Subject: [DOTNET-WINFORMS] Data bound application infrastructure


I want to make my next Winforms app completely data bound, built around the
DataSource objects etc.  I've never had any problems using these features
for grids etc., and only minimal issues using them for detail forms, but I
need some pointers on how to marry the two.  If I'm using a grid bound to a
datatable, e.g. how do I transition to a detail form for the selected item
when my edit command is invoked?  I am willing to do the reading, I just
don't know where.  Too many resources I've spent too much time on only
really cover the grid/list scenarios.