>Hi all,
>
>This is probably old hat, but here it goes...
>
>We were chatting in the ... chatroom and started talking about where the Parent and Child is in a table relation.
>
>He was telling me that where ever the FK is, thats the Child.
>
>After som discussion, my resopnse was, the Parent/Child relationship depends on the type of relationship (1-1 or 1-n). But most of the time, between two related tables, depending on which one you're looking from, you'll have both these relationships. So, the parent depends on what file you are maintaining (by that I mean, doing the Queries, Updates, Inserts, ect.) and that table is the Parent. So, in a 1-1 relationship, the FK is in the Parent and in the 1-n its in the child.
>
>But he believes that it shouldn't matter where you're looking from, you will always have the same Parent and same Child. He reasoned it for a while, but I'm to tired to remember what he exactly said.
>
>I told him thats the way it should be in a Database Container with persitant relations and such, but once you are building data enviroments for forms that maintain a specific file, that changes.
>
>Anyway, what do you think? Are there more possiblities? I could't find anything written down anywhere.

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?