Simple problem/solution I imagine... I feel that I am way overthinking this and can not wrap my brain around it.

Lets say I have Recordset (Table) A. Unique ID and a unique name field.

And I have Recordset (Table) B. Also Unique ID and a unique name field.

Each recordset is a 'One to Many' to the other...

Example, a record in Table A would have many Table B records that should be associated it.

Vice-Versa a record in Table B would have many Table A records linking to it...

How can I set this up so that when viewing a record from Table A I can see the related B records in a portal - and if I jump over to a Table B record I can see the A records which link to it?

When I jumped in to see if it would just come to me, I went with a many to many with joiner Table setup.

Table A

ID

Name

Table J

ID

ID_A

ID_B

Table B

ID

Name

I set up the relationship but couldnt decide what to do next, or if I was even on the right track...

Someone save me from myself! :)

Can you give an actual example of a situation in which this would make sense?

Sure:

A list of Companies

A list of Tags

When viewing a specific company I would want to see which Tags have been applied to it.

When viewing a specific tag I would want to see which companies are being described this way.

Yes, you are on the right track - with a many-to-many, you should have a join table. In some cases, you can get by without one, but then reporting capabilities are seriously limited.

To see the related records from B, place a portal to B on a layout of A, and vice versa. Although a portal to the join table, with some fields from the other "parent" table, might be more useful - see a basic join table demo here:

http://www.fmforums.com/forum/showpost.php?post/246136/

I feel things clicking already Skimming it quick - first blush it appears to be exactly what I need. Thank-you for the quick responses and the clarity!

Will assemble it later tonight and drop in one more thank-you when completed :(