Overall, it is easier to work with individual data tables in a DataSet than
custom business objects. Rocky Lhotka would argue that this is not true OO,
but I see a DataSet as true OO, so I would disagree. The DataSet is a wise
direction to go, especially considering where MS is going with Whidbey.
There is an ASP.NET architecture webcast
(
http://www.microsoft.com/usa/webcasts/) that covers business objects using
DataSets. I am not 100% convinced of the methodology yet, but it is quite
easy to program with. The session is run by Paul Sherriff, and is rather
easy to pick up on. Make sure you look at part 1, as part 2 is more Tips and
Tricks of architecture.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************** ********************
Think Outside the Box!
************************************************** ********************
"DKode" <dk***@cfl.rr.com> wrote in message
news:b1**************************@posting.google.c om...
I have a quick question.
I am redefining a monolithic application i made when I was first
getting into dotnet and have a question about OOP architecture.
I laid out all my objects and came along one sql table that is a
lookup table, but it is used to lookup values in more than one other
table.
does this justify creating this SQL table into it's own object since
it will be used across multiple other objects? other lookup tables are
used in only one object so therefore i decided there is no need to
create seperate objects for them.
any help would be greatly appreciated. thank you.
dkode
