Hi

What are the pros and cons of binding ui elements to db objects (tables
etc.) directly versus binding ui to objects which in turn get data from db?
My app does not have a load of business logic.

Thanks

Regards

"John" <(E-Mail Removed)> wrote in
news:uxfg$(E-Mail Removed):
> What are the pros and cons of binding ui elements to db objects
> (tables etc.) directly versus binding ui to objects which in turn get
> data from db? My app does not have a load of business logic.

Scalability, future upgrades, expandability.

If its not an enterprise type app, or complicated, scalability is the most notable.


--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Blogs: http://www.hower.org/kudzu/blogs

John - if you're using ADo.NET you're going to bind to an object which got
its data from the DB - there is no connected mode support for databinding as
such so there is no direct link to actual tables. the closest you'll get to
connected access is using a DataReader, but it only moves in one direction
so I doubt this is what you'd anyway.
"John" <(E-Mail Removed)> wrote in message
news:uxfg$(E-Mail Removed)...
> Hi
>
> What are the pros and cons of binding ui elements to db objects (tables
> etc.) directly versus binding ui to objects which in turn get data from
> db? My app does not have a load of business logic.
>
> Thanks
>
> Regards
>
>