I'm not completely clear about what you are doing, but it is possible for
one record to refer to another in the same table.
For example, if and event (like a sales fair) arises as the result of
another fair, and you want to track which event gave rise to which other
events, you would add a field to the table like this:
ParentEventID Number
Assuming you already have an EventID (AutoNumber, primary key), you would
then create the relationship like this:
1. Open the Relationship Window (Tools menu.)
2. Add the Events table to the window a 2nd time.
Access will alias the 2nd copy as Events_1.
3. Drag Events.EventID and drop onto Events_1.ParentEventID.
Check the box for Relational Integrity, and create the relation.
In a similar way, you can use 2 copies of the table in a query. In query
design, you can set the Alias property of the table to whatever you want.
This kind of thing is called a self-join. It is quite common for anything
where you trace generations or subassemblies.
Another example:
Self Joins: tables that look themselves up (Pedigrees example)
at:
http://allenbrowne.com/ser-06.html