It sounds like a case for a "Many to Many Self Join" table structure. This
uses two tables: let's call them People and Relations (you can of course
come up with more appropriate names!)

People would have a unique identifier - what you're calling "rcd", though
you certainly should not be thinking of it as a "record number", together
with any other fields of information about the entity. For consistancy I'll
use rcd as the fieldname (note: DON'T use # in fieldnames, it's a date
delimiter).

The Relations table would have two fields of the same datatype as rcd (Long
Integer if rcd is an Autonumber): ParentRcd and ChildRcd. You would add
Relations to the Relationship window once, and add People to it *twice* -
once joined to ParentRcd and the second to ChildRcd. Relations would have a
two-field Primary Key consisting of these two fields; you will probably also
want other fields containing information about the relationship itself
(though if all you care about is the existance of the relationship, perhaps
not!)

This structure will allow each Rcd to be related to any desired number of
other rcd's. You may well need validation rules to (say) prevent a rcd from
being related directly or indirectly to itself (the "I'm My Own Grandpa"
problem); this may require some VBA code in the data entry process, as it's
difficult to create an index or validation rule to search through an
unlimited depth of links.

You may want to consider using a Treeview control to display the data in
these tables.