Gershon, In this case, inheritance will not work. If enter someone as a a member of the 'user' class, which inherits from the 'person' class, they cannot also be a member of the 'client' class, at least not without generating 2 separate entries and having to reenter all the common 'person' properties again. You also cannot change from the 'user' class to the 'client' class without deleting the 'user' instance and creating a new 'client' class.
Mark "Gershon Simcha" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi Theoman > > I think you confuse bettween relationship & inheritance. > Relationship is more like joint tablebles. > The case you describe is classical for inheritance User from Person so you > can apply by a person object to use and vice versa. > One to One relationship is basically an extention of a class (in which case > why not to do one class). > > Hope i did clarify things - Simcha > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.744 / Virus Database: 496 - Release Date: 24/08/04 > >
