Portals would seem to work very well for the first screen.
The second screen could be a portal or a list view layout.
would I still use each week as a seperate field in my table? And does that mean that in my calculations I would need to have 15 different calculation scripts to come up with the Status field?
Sorry if these seem to be simple questions but I want to understand how to set this up and use a calculation field...
The whole point to using a portal would be to avoid separate fields and separate calculations. Each week would be a separate record in the portal.
Ahhh, OK...and you can search by fields ina portal row, I assume...
I will give that a go...
Thanks Phil, Much appreciated...
I am going to go over how to do calculations as I have only done a couple and what I need on this looks to be quite complicated...I guess I will return with more questions...
...and you can search by fierlds ina portal row, I assume...
You can enter find criteria in a portal row, but it helps to understand what results that will produce. When you enter find criteria in a field from a table related to your layout's specified table, you are telling filemaker "find all the records in the [layout specified] table that have at least one related record matching this criteria". Thus, entering "Apple" in a portal field will find all layout records where at least one portal record shows "Apple" in that field. You will still see the other portal records related to these layout records that don't contain "Apple" as long as one record in the portal does have this text.
Thus, you may find that for some searches, it works better to switch to a layout based on the portal records and perform the find there.
I have set up my layouts for the book production schedule and as was predicted searches include all related records. I would like to try the suggestion about a layout based on the portal records. How is that set up?
This forum is great, thanks for the help so far.
all the best,
What I suggested was simply select a layout based on the portal records and perform the search there. You can then design your layout to include fields from the parent record as appropriate. You might place such fields in the header or a subsummary part depending on what you need.
hmm. I am not getting this. I have a portal set up with the fields as in the first mock up. This portal shows all of the weeks of a term.
I then made a layout with a portal that has one portal row, hoping that I can just search for a particular week and have those results show, then using list view I would get a list of all the records for the searched for week, like the second page of my mock up.
What I get no matter what week criteria I put in is all of the related records that have my searched for week in them. So if I searched for week 4, the records that show up in my single portal row layout all start at week 1.
I understand that I don't understand...If you know what I mean...:-)
This is really close to working...
Can you give me a few more hints at what I need to change??
Do not use a portal for this.
Create or select a layout that lists the portal records' table in the "Show records from" box in Layout Setup...
Perform your find there.
ahhhh, OK I will give that a go...Thanks Phil!
works like a charm...
Shall I call this complete and start a new thread for the calculation field??