Jerry,

Just to clear something up:

If we had, say, an Address table, and each address references a State and a County (Both in their own look-up tables), i.e. the address table only has the FK to a state and a county, then WHICH to you is/are the parent(s) and child
table(s)?

If you are moving through the address table, then I would say you are moving through a Child table, as one county or state rec will have several address recs, 1-to-m, in normal circumstances.
If you reverse the reln., in code (without altering the persistant relns in the ERD you understand) and relate the county & state, via their (normally) PKs, to the (normally) FKs of the address table (1-to-1 basis), pointing rigidly to one specific look-up rec for each address rec, then as you move through the address table, each approp. state and county rec will be fetched.

>Terry:
> I totally misunderstood... I'm sorry.
> I started to do what you said, reversing the Parent-Child Relation, but then realized that it wouldn't work because I need to isolate the data to just one record in the Parent table. If I reversed the tables' Relation, all of the data would be there.
> Setting a Filter would work, but it would slow everything down.
>
>Jerry