If you were to enter layout mode, make a copy of the start date field object in the portal row and drag it up to take the place of the start date field to the right of Course Type, it would automatically show the start date of the first row of your portal if it is unsorted. To make sure that this is the earliest start date, you can specify a sort order in the relationship that sorts by Start date. With that setup, you could also define the start date field in CRS as a calculation field that simply copies the value of the related start date, but you might not even need that field given the fact that you can just refer to the related detail record's start date field in many contexts such as this layout.
And with that sorted relationship, there are two ways to show the needed end date:
Use a one row portal to the details table and sort it by end date in Descending order. Place the End Date field from Details in this one row portal.
Define the End Date field in the CRS table as:
Max ( CRSDET::End Date )
Hmmm, come to think of it, Min ( CRSDET::Start Date ) could be used to show the earliest start date even with out any sorted relationship being used.
Maybe you can make the Start and End Date fields in the Course table into calculations that simply reflect what's in the Course Details table:
Thank you both philmodjunk and Jaymo,
Yes using Min and Max worked wonderfully once I realized that in order for it to work (and this is the embarrassing part) you have to pay attention to that area at the bottom that says "Calcualtion result is ..." AND once I changed it to date it worked.
Why doesn't Filemaker recognize the field and change the "Calculation result" especially if there is only one field???