Kevin Brown wrote:
>
> In relational database design you DO store a seperate key for each. :-)  The
> one to many relationship (again, in traditional DB design which doesn't have
> much bearing on this anyway) simply means that one item can 'contain'
> multiple items.

OK, I guess I was thinking that for a one-to-many you would do a lookup
on the child like child.fldX == parent.fldY  (where fldX is not a key
field
as such). But I'm probably talking nonsense.

[snippage]
 
> 
> Hope I'm clearer this time.

I think I understand.


Hal