Application design (data tier)

[therealmccoy]

I am working on a database application that I call MultiBase. The jist of the application is that it will load a database and create a GUI to interact with it. The application also impliments search and reporting capabilities. The application is currently a winform application, but I plan on implimenting a web interface at a later date. I have started writing a DLL to handle the database access. I'm lost as to if I want my DLL to return a dataset and then have a seperate class (? business logic ?) handle the bindings (and currency manager) or if I want to just return a datarow and somehow bind that to my winforms controls (don't think I can bind a datarow to a control, I would have to come up with some other way). So my question is: In implimenting a n-tier (or 3 tier) applicaion what is the best way to present the data from the data tier to the presentation tier (via the business logic tier ?) ? I'm thinking of returning a dataset to my record class (that handles the bindings and currency manager) If a new record is added, then send the dataset back to the data tier via the record class (which I would call my business logic). Any thoughts? www.lovethosetrains.com