One-to-One relationships in an ADP

[dmh_test1]

Hi, for the first time in my career I have a legitimate need for a one-
to-one relationship between tables. I see no way to set op a one-to-
one within an ADP project, however. Do I need to write a trigger to
enforce a one-to-one, or is there an easier way?

[Rich P]

for a one to one relationship, just add a unique key in the primary
table so that you cannot have a duplicat record with the key values.
Then, in the support table, add a unique key there so you cannot have
duplicate values. Then add your relationship and enforce referential
integrity. Now you have a one to one correspondence.

Rich

*** Sent via Developersdex http://www.developersdex.com ***

[Tom van Stiphout]

On 29 Jan 2007 18:32:16 GMT, Rich P <rp*****@aol.comwrote:

And be sure that you create the relationship with the correct table on
the one-side, and on the "many" side. For example if I have an
Employee and Salary table, it should be from Employee to Salary, not
the other way around.

-Tom.

>for a one to one relationship, just add a unique key in the primary
table so that you cannot have a duplicat record with the key values.
Then, in the support table, add a unique key there so you cannot have
duplicate values. Then add your relationship and enforce referential
integrity. Now you have a one to one correspondence.

Rich

*** Sent via Developersdex http://www.developersdex.com ***