Speak it out in sentences, that's where your relationship structure comes from.
One Project has many meetings.
One meeting has many minutes
One meeting has many actions
From all of that your tables are:
Projects, Meetings, Minutes, Actions
and your relationships are:
Projects::id = Meeting::ProjectID (one to many)
Meeting::id = Minutes::MeetingID (one to many)
Meeting::id = Actions::MeetingID (one to many)
Minutes and actions "inherit" the project they belong to from the meeting being related to the project.
So essentially, you can create a Meeting detail layout, with portals for Minutes and Actions.
On your Project page, you can create a Portal displaying meetings.
You can also display portals for Minutes and Actions on the Project page, since they're inheriting the relationship from Meetings.
For Actions and Minutes, check the box for "allow new records to be created via this relationship" and you'll be able to enter in new Actions and Minutes straight from the Meeting detail screen.
Thank you so much I will work with this…just getting a little overwhelmed and feel that if my relationships are correct I can fiddle around with the layouts from there. Can I ask you more questions if needed? Also, the projects is a file separate from the meetings if that makes a difference. Basically what I am doing is adding the meeting file to the already existing database solution that includes a file for Projects, Communications, Contract Documents, Contacts, Staff, and now Meetings.
Just post specific questions here. The more specific, the better answers you’ll receive. If you need someone to advise and train you on a more one-on-one level, you should probably seek out a mentoring developer for the best results.
As for using data from other files, you can just add those table occurrences to your main file. Just make sure the that users logging in have the correct access in both files.
Can I put a “project” field in the minutes data entry layout. I can put it in the meetings details layout.?
So I want to have the project number and name field from the projects database to show in the minutes table layout, but the minutes is not directly related to projects, it is related to meetings details which is related to projects.
If your relationships are as specified earlier and you have the necessary match fields populated, then a layout based on the "many" side of a relationship can include fields from a TO on the "one" side of the relationship without issue. It works the other way around as well, but when there are many related records and you just put a field from that TO on the layout, you only see data from the "first" related record--and that can be an issue.
So in your case, go right ahead, it should work just fine.
Yes I have it working now. Thank you
And how do I mark this question as answered?
Just one more observation about this…..
In my minutes layout I have to include the meetings id_fk in order for the fields from the meetings to show in the minutes layout.
What if I had a relationship like:
Meeting::id = Minutes::Meeting Id
Minutes::id = Meetings::Minutes id
Would that create a loop of some sort?
You should not have to include that field on the layout unless you also have to enter a value into it to link the record to a record in Meetings. Other than that, you shouldn't need this field on your layout at all.
And what you show is not possible in a FileMaker relationships map. You'll get the system forcing you to open a new occurrence of one of the two tables to prevent creation of a loop.
And I don't see what such a relationship would accomplish for you in the first place.
Sorry the field is actually from the projects database but coming thru the meetings and into the minutes layout. So I can keep track of what minutes to with a project ( Project # would be 1306, meeting #1, minutes would show 1306 in one field and 1 in another. It is working in a round about way I guess. I created a script to copy the meeting pkey to the minutes and then I can show a field from the projects database.
Does this represent your relationships?
Projects::__pkProjectID = Meetings::_fkProjectID
Minutes::__pkMinutesID = Minutes::_fkMinutesID
Actually, I do not have the last line (Minutes::__pkMinutesID = Minutes::_fkMinutesID)
What I was doing was:
Minutes::_pkMinutesid = Meetings::fkminutesID