B
Bob Palank
Deae Dr. GUI, MVPs and others
Features of VB.Net 2005 makes it so easy to access mdb tables directly from
the form's controls. This makes me wonder how and if I should restrict the
communication to and from a database tables to a separate data tier which
is reached through a business process logic tier which passes data back to
the presentation tier.
1. Is three tier separation a best practice and recommended in all
solutions
for systems with a complexity level of seven or more classes ?
2. Doesn't the application of the point and click convenient access to the
DB Tables somewhat negate three tier
application solutions?
3. Sheepishly, could I say a new direction is for the presentation tier to
engulf the business
rules tier as well as the data access tier ?
BR
Bob
Features of VB.Net 2005 makes it so easy to access mdb tables directly from
the form's controls. This makes me wonder how and if I should restrict the
communication to and from a database tables to a separate data tier which
is reached through a business process logic tier which passes data back to
the presentation tier.
1. Is three tier separation a best practice and recommended in all
solutions
for systems with a complexity level of seven or more classes ?
2. Doesn't the application of the point and click convenient access to the
DB Tables somewhat negate three tier
application solutions?
3. Sheepishly, could I say a new direction is for the presentation tier to
engulf the business
rules tier as well as the data access tier ?
BR
Bob