Hello everyone,

I'm with a lot of questions about how to design a n-Tier, how to do
the code how to organize, and all the samples that i find, are with
only one table, one class with DataAcess, i need something more
"Complex"..

maybe you guys have a little sample with maybe a User class, and a
UserGroup class that is related with the User class...and a Project
class that is connected with a Client class that is connected with a
ClientContacts class...and the Project class have a ProjectStatus...

my biggest doubt is what should i do when designing them???

is this right?

   public class Client
   {
       private string _Name = string.Empty;

       public string Name
       {
           get
           { return _Name; }
           set
           { _Name = value; }
       }

       public void Insert() {
           //Access to DAL
       }
       public void Delete() {
           //Access to DAL
       }
       public void Update() {
           //Access to DAL
       }

       public class Contact
       {
           private string _Name = string.Empty;

           public string Name
           {
               get
               { return _Name; }
               set
               { _Name = value; }
           }

           public void Insert()
           {
               //Access to DAL
           }
           public void Delete()
           {
               //Access to DAL
           }
           public void Update()
           {
               //Access to DAL
           }

       }

   }

because that sucks...

i have to declare the Client class...if i want to access the Contacts
form a Client i have to:

Client.Contact Contact = new Client.Contact();
Contact.Name..etc..

need help please...

thanks in advance...