If you are using FileMaker 13, you can use the new "list of" type summary field to get this list. You can set a field or a variable to the value of this summary field if you need to capture this list.
In FileMaker 12 or 13, you might also be able to produce the same list using ExecuteSQL by replicating your search criteria as the WHERE and Join clauses of the SQL expression.
In all versions, Copy All Records, if executed on a layout where the field to form the list is the only field on the layout can produce such a list in the system clipboard.
And a looping script can loop through the records and use list or other calculations to build the list.
Thanks. After testing, it appears the List() aggregate does work on found sets. I had understood the documentation to say it didn't , but it does and all is great!
Better check again. the List function works on sets of related records not the current found set.
I then don't understand what I am seeing, or perhaps I'm not clear on the meaning of "sets of related records" vs "found set" in this context.
I constructed a test database with one table with three fields: id, fruit, fruitlist where id is a simple numeric id, fruit contains the name of a fruit, and fruitlist is a summary field "List of fruit". I populate the list with a few fruits, including "apple" and "apricot".
If I Show All records, fruitlist contains all the fruit names in the table. If I Find fruit names beginning with "a" and fruitlist contains just "apple" and "apricot".
What am I missing?
It's just a matter of our using the same term to mean something different.
After testing, it appears the List() aggregate does work on found sets.
The "list of" Summary field is what you tested and it is indeed based on the current layout's found set.
The List() function is something else and is not based on the current layout's found set.
Looks like where I went wrong was confusing the term "aggregate" with "summary" and that lead me down the wrong path in searching online documentation. Thanks for your help!