relationships one to many or indeterminate

[Aaron Schultz]

ok well i am designing a database for my business and i have been using
lynda.com for help but when i came to an error message i couldn't find a
person to talk to so i figured you guys could help but anyways

every time i try to create a one to many relationship it tells me that im
creating a indeterminate relationship but i dont think that is my problem the
problem i am having is when i click create it tells me that (No unique index
found for the reference field of the primary table) the error code is (error
3609) i hope this will help thanks have a great day

 

[david]

When you try to create a one-to-many relationship, there can only
be ONE of each record on the ONE side of the relationship.

For example, you can declare a one-to-many relationship between
1 and 1,1,1,1
2 and 2,2,2,2
but not
1 and 1,1,1,1
1 and 1,1,1,1
If there is more than one 1 on the ONE side, the relationship is
indeterminate, not one-to-many.

To ensure that there is only ONE of each record on the ONE side
of the relationship, you should put a Unique Index on that field.
Open the table in design view, click on the field, set the index to unique.

(david)

 

[John W. Vinson]

On Tue, 2 Jun 2009 20:52:01 -0700, Aaron Schultz <Aaron

ok well i am designing a database for my business and i have been using
lynda.com for help but when i came to an error message i couldn't find a
person to talk to so i figured you guys could help but anyways

every time i try to create a one to many relationship it tells me that im
creating a indeterminate relationship but i dont think that is my problem the
problem i am having is when i click create it tells me that (No unique index
found for the reference field of the primary table) the error code is (error
3609) i hope this will help thanks have a great day

There must be a unique Index on the joining field in the "one" side table. The
usual way to ensure this is to assign one field (often, but not necessarily,
an autonumber field) as the Primary Key of that table, and use that primary
key field in the relationship. If you use an autonumber the joining field
("foreign key") in the other table needs to be a Long Integer number;
otherwise it must be of the same datatype and size as the primary key field.

My guess is that you have just not defined a Primary Key in your table.

 

[david]

I can't set up window live email?