Hi,
I am also trying to come to grips with 3 (N) Tier structures.
On the MSDN web site there is an example:
http://msdn.microsoft.com/library/de...ldntierapp.asp
It is titled "Building an N-Tier Application in .NET"
By "Paul D. Sheriff
PDSA, Inc."
Paul suggests:
All Data access routrines should be exposed as objects instead of function
calls
SQL should be eliminated from the client side code
It is a good article and well worth reading. I am having problems following
the instructions to create the data layer as I am not getting the choice of
Project Template recomended.
"WStoreyII" <WS*******@discussions.microsoft.com> wrote in message
news:23**********************************@microsof t.com...
I have a project that i am trying to create using three tiers
data Tier: Access Database
data Access Tier:
and a User Interface Tier:
My question concerns the data access tier. When creating a project of
this nature
is it better to create objects that represent the data and create
collections and at runtime load the data in to these objects and
manipulate it that way or would it be better to just create queryies or would both of
them be fine?
I really am new to this so any thing that you could offer or direct me to
would be of a great help. Also
what would be better for the data tier Access or Xml ? Why?
Thanks
WStoreyII
