Hi,

When you connect to a database and retrieve data, ususally
that data is displayed in a textbox, listbox, grid, etc.
The books I've read usually to this. But shouldn't a class
be created, then have the data populate the class then
display it. For example, instead of having employee
information - name, pay, etc., retrieved by a datareader
and displayed in textboxes, should an Employee class be
created first? Then the information from the database
could populate the Employee class or a collection of
emplolyee classes be displayed.

Does anyone know of books, examples, or other resources
that discuss this?

TIA,
Tarey

Tarey,

YES!

It is unfortunate that so many examples try to make things so simple that
they do it in a way that's just wrong for the real world.

You might try www.fawcette.com. There are numerous articles on MSDN, just
hard to sort through them. I just bought Rocky Lhotka's book (haven't read
it yet).

--
Kathleen (MVP-VB)



"Tarey" <(E-Mail Removed)> wrote in message
news:002501c34bc2$8118ca50$(E-Mail Removed)...
> Hi,
>
> When you connect to a database and retrieve data, ususally
> that data is displayed in a textbox, listbox, grid, etc.
> The books I've read usually to this. But shouldn't a class
> be created, then have the data populate the class then
> display it. For example, instead of having employee
> information - name, pay, etc., retrieved by a datareader
> and displayed in textboxes, should an Employee class be
> created first? Then the information from the database
> could populate the Employee class or a collection of
> emplolyee classes be displayed.
>
> Does anyone know of books, examples, or other resources
> that discuss this?
>
> TIA,
> Tarey
>
>

Check out this book:

Expert One-on-One Visual Basic .NET Business Objects
by Rockford Lhotka

"Tarey" <(E-Mail Removed)> wrote in message
news:002501c34bc2$8118ca50$(E-Mail Removed)...
> Hi,
>
> When you connect to a database and retrieve data, ususally
> that data is displayed in a textbox, listbox, grid, etc.
> The books I've read usually to this. But shouldn't a class
> be created, then have the data populate the class then
> display it. For example, instead of having employee
> information - name, pay, etc., retrieved by a datareader
> and displayed in textboxes, should an Employee class be
> created first? Then the information from the database
> could populate the Employee class or a collection of
> emplolyee classes be displayed.
>
> Does anyone know of books, examples, or other resources
> that discuss this?
>
> TIA,
> Tarey
>
>