I did look at the site. I checked your Units table on the backend, and the "Related Data" we told you would be there, is there.
To provve this, I just enabled 'view' and 'add' for "Events" under Related Data on your Units table. Take a look at your Units table, on the front or back end, you will see two new columns.
The 'view' link will open a filtered table on the Events table, showing all events for that unit row. The 'add' link will bring up a new Events form, with the link to Units pre-filled.
This is what we call 'faceted browsing', as described to you by both myself and Rob in this thread. It may or may not be what you want to do. But it's hard to tell what you need, when we tell you to try something and you don't try it.
My apologies for thinking you might have been using InnoDB, but in the MySQL world, Foreign Keys are an InnoDB invention. Google "MySQL foreign keys". It would make things simpler and avoid confusion if you refered to them as 'joins' or 'join elements'.
I understand your frustration, but please understand mine. Go back and read this thread, and put yourself in my shoes of trying to understand exactly what you are trying to do. Bear in mind that you are living and breathing your one app, whereas I'm trying to understand your app structure and requirements from a standing start, whilst simultanously doing the same for numerous other users.
So, as I said, lets take a step back and establish exactly how you need to structure your app. There are other ways of achieving what you want to do, specifically to build "real" one-to-many relationships between your tables. See the "widgets and gidgets" example here:
http://fabrikar.com/forums/showthread.php?p=30558&highlight=widgets+gidgets#post30558
... which was written for 1.0.x, but applies to 2.0 as well. Rather than immediately trying this on your existing tables, I'd suggest building a quick widgets/gidgets example so you can see what this does for you.
-- hugh