stxlen

I have attached a file. Hopefully the description on the form page explains what I am looking to do and the comments in the Relationships Tab explain enough. RosterManagement.fmp12

I think this may be the route I'm looking for, but I guess it's my understanding of how portals filter. In my mind, it's an additive/subtractive process. So above... Table 1 to 2 filters to keep only active individuals, and then 2 to 5 takes only active individuals and further filters to only retain attackers. But this is not how it seems to behave, 2 to 5 takes all records and keeps attackers, regardless if they are active or not. So if I' thinking through this properly, my filtering process must be done via one relationship - one step, instead of the two steps I'm using - and then any grandchildren from there need just be to look up related records on a one-to-one relationship?

Been awhile since I picked up FileMaker so I'm sure I'm missing some simple logic here but could use some help I would like to display a portal with grand-child records. I am using relationships to filter records. I am trying to show the status of who is out (unavailable) to train in one portal, and in another, who is active (available) and is an Attacker. The out table is working, but it's the active and attacker that is not. I've been walking through my tables/relationships to see where it is breaking.... This image shows that my first few filters are working. 99B65... is the foreign key that links a player's status to the training session. So you see Portal 5 has the wrong foreign key, and is just grabbing the first related record. Portal 1 shows I'm grabbing all players for that date correctly Portal 2 shows I'm grabbing Active players correctly Portal 3 shows that I'm grabbing Out players correctly Portal 5 shows I am not grabbing Active and Attackers correctly. Here are the relationships: So it's the relationship between 2 & 5 that isn't displaying properly.... or, which is more likely, I'm not using the correct table on the portal perform this filter.

I would like to hide the Menubar and Toolbars except for the Quick Find feature (I'll take all the find features if you can't specify just one). So far the only way I can see how is to: Show the MenuBar Make a Custom Menu Set for users that removes the ability to Create Records, etc. But the above requires me to then modify all user scripts to run with full access privileges as I've scripted the creation of new records.... And also to question whether this will affect any portals that utilize "create new records via this relationship" Am I missing an easier setup?