Ahhh, excellent.

Thanks for the answer Helen, I just had a feeling I may have been
over doing something. This makes sense.

Quite obvious I've come from a Paradox background, hey?? :)

Rgds,
-Ryan

> Hey, this isn't Paradox, which relies on hierarchical keys! use

the

> generated unique column keyF as the primary key of the detail

table and let

> the foreign key to the master do its work uninhibited. The PK of

the

> detail table is irrelevant to the FK relationship and there are

101 reasons

> (erm...a slight exaggeration) not to have the PK and the FK

columns

> stepping on each other.
>
> Also, you can have multiple FKs in the detail if you want to, and

let the

> same detail table be detail to different masters. You can't

achieve this

> with Paradox-style keys.
>
> What you have (minus the composite primary key) is ideal.
>
> heLen