Trying to create a One-to-Many relationship but it will only make a One-to-One

[bell]

Hi All,



I have three tables: Wirelist Cover, Revision History, Wirelist


Wirelist Cover has one key: Document Number (text)

Revision History has two keys: Document Number (text) and Rev (text)

Wirelist has two keys: Document Number (text) and Wire (number)

I was able to make the Wirelist Cover to Wirelist relationship One-to-Many (since there can be multiple wires per Document Number)

I am NOT able to make the Wirelist Cover to Revision History relationship One-to-Many....it keeps coming up as One-to-One

I need the relationship to be One-to-Many since there can be multiple revision (they are alphabetical revision, starting with -, A B C...etc) per Document Number

I dont know why it wont show as a One-to-Many. It sounds like I only declared one key in the Revision History table, but I looked and there are definitely two keys listed.

Is there a problem because Rev is defined as text??

[June7]

Why are you using compound keys?

Can't link RevisionHistory and Wirelist on these compound keys.

Suggest you use autonumber as PK and save as foreign key. Set the data fields as compound index to prevent duplicate.

[orange]

Can you describe to readers, who do not have any knowledge of your business nor your current opportunity, what a typical day consists of in your environment?
Wirelist, WirelistCover and Document seem to be jargon for your business. Until readers have some context, there will only be guesses to solution.

Good luck.

[bell]

Why are you using compound keys?

Can't link RevisionHistory and Wirelist on these compound keys.

Suggest you use autonumber as PK and save as foreign key. Set the data fields as compound index to prevent duplicate.

I'm still fairly new to access, so I didn't even know what a compound key was.

After doing some more research, I understand my problem. I ended up doing what you said, added auto number keys to my tables and used indexes to prevent the duplicates.
All works now.

Thanks