I am working on a software requirements database and want to be able to
relate requirements to one another, so that the reader can easily see what
other requirements may duplicate or impact a given requirement.  These
requirements do not have a hierarchical relationship, I am trying to merely
associate them as peers of one another.

I have set up an intersection table tix_ReqReq with the following structure:
ID (Autonum)
ReqIDA (the originating requirement, i.e., the requirement displayed on the
main form to which other requirements are associated via a subform)
ReqIDB (the requirement associated to the originating requirement)

I can display (in a form and report) the requirements associated with the
originating requirement, but want to be able to leverage the relationship
specified in both directions.  For example, if the table has the following
values

ID   ReqIDA      ReqIDB
1      512            613
2     512            522
3     613            499
4     199           211

I want to be able to see on the form/report for Req 512, that it is related
to requirements 613 and 522 (straightforward) and on the form/report for Req
613 to see that it is related to requirements 512 and 499 (harder).  How do I
make this work?

Thanks in advance.