I would recommend you back up, if you haven't already done this, and use an actual ERD design tool rather than rely on the Relationships graph for data modeling for anything other than the simplest data design. A data model is a time-consuming portion of any "real" application and needs to be done using a tool for that purpose.
Using SQL Editor (an inexpensive tool that runs on the Mac), you can (a lot) more easily do data modeling. While you model the data, the tool generates the DDL for you as well.
And, YES, SQL Editor works with FileMaker!
P.S. Below is a simple M:M design I did in SQL Editor
to solve this problem you need to think in the data layer instead of the presentation layer..
Many to many entity relationships are usually solved with a join table.Many-to-many (data model) - Wikipedia, the free encyclopedia
I meant to also include in my posting above that SQL Editor will CREATE the FileMaker database for you once you model it.
Navicat and other much more expensive tools also do data modeling, but SQL Editor is the only one I know that works specificially with FileMaker (Oracle, MySQL, SQL Server, ...).
In fact, here are SQL Editor's supported databases:
Good morning donselaar,
I hope your day is going well. I think the relationship example that Morkus provided is a good strategy to use. I've created several solutions that have very similar goals to the ones you described. In those, the layouts for certification documentation/reports were primarily based on the training event table - studentcourse table in Morkus' example. It was also helpful for me to approach these projects with the thought that the student - authorized people, in your case - was the central component or hub of the design. Devices change and so do applicable training courses, but the student and their associated training events never do. Have a great day!
Wow! this looks promising. Have you tried it?
If you mean have I tried SQL Editor, yes. I've been using SQL Editor for years as well as data designer in Navicat (or Erwin for large Oracle projects).
SQL Editor is inexpensive, has been around quite a while and gives a data modeler a real tool to model a database.
I worked with the developer of the product a while back to fix a FileMaker issue it had creating the actual FileMaker database. It worked fine after that update.
Post back your comments on the tool. (Other than being a registered user, I'm not associated with SQL Editor company in any way.)
I haven't tried it, but it does look good.