So long as you are using the entire PK fileds from one table in the Constraint clause you can then match those fields to the fields in the References clause, without any problem.
>From your sample I thought you wanted to go the opposite direction. You will not be able to map bi-directional relationships, though John Davidson On Sat, Oct 16, 2010 at 6:31 AM, IsNull <[email protected]> wrote: > Btw, about not possible, I'm able to run this: > > > ALTER TABLE Customer > CONSTRAINT someName FOREGIN KEY > ( > [AdressID] > [Mandator] > )REFERENCES Adress( > [AdressID] > [Mandator] > ) > GO > > > The two tables look like: > > TABLE Customer( > PK Mandator > PK CustomerID > > Name > AdressID //<--- foregin key to Adress Table > > ) > > TABLE Adress( > PK Mandator > PK AdressID > > Street > PLZ > ) > > So, whats the diffrence here? This works under SQL 2000. I'm really > confused right now. > Thank you for any assistance so far. > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
