There are obviously many ways to this but we like
to take the approach of seperating the Data Layer / Business Layer /
Presentation Layer. We also often have the need for multiple UIs working on
the same underlying Business Object - with databound controls you often find a
lot of business logic tied into the GUI, making it difficult to easily create
alternative GUIs. In addition, I suspect that databound controls may also
complicate backend database independence. Also, with databound controls any
small change to the database could have a direct impact on the
GUI.
Just another view...
Xander
----- Original Message -----
|
- [DUG]: To Bind or Not to Bind Jeremy Coulter
- Re: [DUG]: To Bind or Not to Bind Neven MacEwan
- Re: [DUG]: To Bind or Not to Bind Mark Derricutt
- Re: [DUG]: To Bind or Not to Bind Neven MacEwan
- RE: [DUG]: To Bind or Not to Bind Max Nilson
- Re: [DUG]: To Bind or Not to Bind Xander van der Merwe
- Re: [DUG]: To Bind or Not to Bind Steve Peacocke
- Re: [DUG]: To Bind or Not to Bind Mark Derricutt
- RE: RE: [DUG]: To Bind or Not to Bind vss