Multiple autonumbers?

[katiekat]

Hey all,

I have three linked tables, and it ends up that the one in the middle needs to have two unique identifiers within it. I would rather the users didn't enter the id #, but two autonumbers in one table is impossible. Should I just re-think my structure, or is there a way around this?

Thanks for the help!! : ) Holy tek-tips batman!:-0

 

[LittleSmudge]

It sounds like you are desperately in need of an urgent structure re-think.

Come on - tell us the problem and we'll sort out your structure.

G LS

 

[katiekat]

well, here goes!

I have three tables. One holds assignment info (A), one holds company and contact info (B). Table (C) will eventually hold contact info taken from (B), eliminating huge amounts of repeating data. The goal is to have a static relationship between (A) and (B), and have (C) able to be updated without causing damage to the initial info related in (A). Yikes.

Any help would be appreciated!

Kate Holy tek-tips batman!:-0

 

[katiekat]

I realize this is complicated, and if I have not explained myself well enough, please let me know.

Thanks! Holy tek-tips batman!:-0

 

[LittleSmudge]

Sounds okay to me Kate ( As a first pass - anyway )

The process of converting tblB into tblB and tblC is a goos step towards Normalisation.

tblB should already have a Primary Key ( BId )
So in tblC you need a Foreign Key of exactly the same data type and size and tblB.BId
This then creates a One-to-Many relationship between the two.
One Company in tblB can then have none, one or many Contacts in tblC.

So far - so good.
So now I need a bit of extra explanation on the relationship that you are trying to achieve between tblA and tblB

Is it One Assignment to Many Companies
Is is One Company to Many Assisgments
Both, Neither, .. ..


G LS