What you have is both a many to many relationship and a self join.
You need two foreign key fields in Table C, not just one.
Start with these relationships:
A::__pkA1 = C::_fkC3
B::__pkA1 = C::_fkC4
You can place a portal to C on the A layout to list and select a B record for each given A record. Fields from B can be included in the Portal to show additional info about each selected B record and the _fkC4 field can be set up with a value list for selecting B records by their ID field. And a field in Table C can identify whether the related person is "Father, Mother, cousin, etc."
I see my mistake. Works well. Thanks again very much PhilModjunk.
Is this a simple familiar relationship database or a genealogical database?
I ask because I started a Family Contact database that would relate individuals to families.
The depth of the family relationships was fairly shallow, but the number of tables, table occurances, and relationships grew and grew.
I found a fellow with a genealogical database that was looking for beta testers, the beta's design table was scary (I am easily scared)
It is intended to be a simple family database with maybe 2 generations, not a full bore genealogical database. Do you offer yours for license?