Teoman Try
Establish one- many relationship and define an unique index on the many side of the relationship. Regards Sukesh Teoman Haliloglu <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi, > > I've been trying to implement kind of a "one-to-one" relationship between > Person and User classes. > > If I choose to have a relationshionship (there's a bug there in the new > property wizard, even though you choose "one other object" as the > relationship type, cardinality in the second class is written as "many", I > had to correct it to "one" by hand); although not every person is a user, I > cannot set the User property of a Person to nothing, %Save method generates > an error. (that's normal if one-to-one relationship forces you to have a > User for every Person and vice versa. Is this the case?) > > If I choose to have plain object references in each class, then I have to > implement the relationship that I want to have manually, i.e. while saving > an object, setting the corresponding property in the other class. (I want to > have a User property in the Person class and a Person property in the User > class as I'll need to get the other object's properties frequently) > > Of course I can only have a User property in the Person class, then > everytime I need to find the Person properties of a User, I need to do a > query. (I know that I can set it up as a calculated property)... But I > thought I could implement it with a relationship.... > > Any hints? > > Regards, > Teoman > > > >
