Make sure that Memo::DateX, People::Date1 and People::Date2 are all fields of type Date when you check them in Manage | Database | Fields.
If you define this calculation field, cDateList in People like this:
List ( Date1 ; Date2 )
and select TEXT as the result type, this field must be a stored/indexed calculation; you can define this relationship:
Memo::DateX = People::cDateList
And a portal to People will display any record where the date in DateX matches either Date1 or Date2.
You can then define your value list to list dates from cDateList to get a value list of all dates.
Limiting your value list to just dates for a given year will be tricky. Many of the options you might use for that will result in cDateList becoming an unstored calculation which then can't be used in the relationship needed for the portal, nor in the value list of dates. You may need to use a script with Replace Field Contents that sets and clears a field in each people record to include/exclude the Date1, Date2 values in/from the value list.
Thanks - This is ok, and I had it set up with the TEXT type, but the problem here is how Filemaker sorts textualized dates... they show up in an order like this:
And I get why this happens - they are no longer treated like dates (or numbers for that matter). Any advice on getting the list to display chronologically?
IF the text listed in the value list had this format:
they would sort correctly into alphabetical order. It is possible to set up some calculations inside the list function to produce this text from each date, but you then will have issues when you select a date from the drop down. You would need a script trigger driven script (OnObjectValidate) to reformat the entered text into a valid date format before FileMaker's built in date validation can kick in and display an error message.
Right ( "0" & Month ( dateFIeld ) ; 2 )
will return the needed leading zero for single digit months.
Thanks - Looks like a great mod for a different kind of project and I may implement this for a differen endeavor. Out of preference for simple solution, I'm going to use a calendar selector for the DateX field. This keeps things clean (ie, no list that would continually expand, and no trigger scripted validations), although at the expense of the user needing to know the date in question - which, in our case, should be ok.
Thanks for your help - have a great day.