Since it's still Friday, I must reply in rhyme
(Last time I checked it was 11:50, so there is still some time).
Just because a table has an FK, it ain't always a child,
In a 1-to-1 it may be a daddy, to phrase it very mild.
And then you have a self-join, where anything can go.
So tables are not always set in relational positions, you know.

So just kick back and use
the relation that makes things correct.
Of the notion do not abuse,
that relations are always set.

>>There are times that one usesthe same table in two work areas and sets a relation from the table into itself. So which is the parent and which is the child on a persistent basis?
>
>On a persistant basis it would be whereever the FK is, is the child. Since in the DBC there really isn't multiple aliases, this doesn't truly apply, but I know what you mean, good point/