One-to-Many not working...

[Cazca]

this is probably an easy easy fix, but i just can't seem to figure it out.

the goal is to have subdatasheets, but I can't get the one-to-many to work form TblCONTRACT to TblCLIN






There should be one(contract/task order) to many (CLINs) and one (CLINs) to many (FTEs)

Can anyone help?

[ItsMe]

...I can't get the one-to-many to work form TblCONTRACT to TblCLIN...

You have a One to One relationship defined.

[Cazca]

shouldn't it automatically define a one to many. This is what it did for me when i set the relationship between CLIN and FTE tables.

can u manually change this?

thanks for the quick reply, btw

[ItsMe]

I think the issue is that you have a conflict with CLIN and FTE. If you already defined a one to many with that, the other would have to be one to one. Maybe what you are in need of is another table, a junction table to provide a many to many option in there somewhere.

[ssanfu]

Linking two tables on primary key (PK) fields will result in a one-to-one relationship.

A one-to-many relationship is linking the PK field in one table to a foreign key (FK) field in a different table.
The PK field must have unique values. The FK field must be the same data type and not a PK field.

While you can have text type fields as PK fields, it is usually better to have Long Integer type fields as PK fields.
See:
Microsoft Access Tables: Primary Key Tips and Techniques
http://www.fmsinc.com/free/newtips/primarykey.asp



Also, you should not use spaces, special characters or punctuation in object names. Only letters, numbers or the underscore.

[Cazca]

Thanks ItsMe. I was able to get it to work... the issue was linking two tables on one PK like you mentioned.

I'll remove the spaces as well. Thanks for the help!

[ItsMe]

Glad to hear.