[AccessD] Switching to VB.net

Not to be confused with N-tear(ed) which describes the many levels of
weeping and gnashing of teeth generally associated with every M$
architecture.

Jim Hale

-----Original Message-----
From: Charlotte Foust [mailto:cfoust at infostatsystems.com]
Sent: Friday, September 22, 2006 9:28 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Switching to VB.net


N-tiered design just separates the presentation tier from the data tier
and the business rules.  They're pretty much bundled together in Access,
but for enterprise solutions, network solutions and web-based solutions,
n-tier is the way to go.

Charlotte Foust 


***********************************************************************
The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or
other use of or taking action in reliance upon this information by
persons or entities other than the intended recipient is prohibited.
If you have received this email in error please contact the sender and
delete the material from any computer. As a recipient of this email,
you are responsible for screening its contents and the contents of any
attachments for the presence of viruses. No liability is accepted for
any damages caused by any virus transmitted by this email.