I've created a valuelist that uses 2 fields for the valuelist:
Record ID and DescriptionSummary
The value list is set to only show values from the 2nd field - DescriptionSummary.
The Record ID is the primary key field and DescriptionSummary is an unstored calc that displays a summary using a few related fields. When I select DescriptionSummary as the 2nd field when setting up the value list I get the message that:
"This value list will not work because the field "DescriptionSummary" cannot be indexed. Proceed anyway?"
I click OK and continue on and test the value list and it appears to work just fine - I chose the DescriptionSummary field knowing it was an unstored field and expected to get this error message, but as far as I can tell the value list is working and showing the correct values so far in my testing. Is there any reason why I can't continue to use this value list despite the warning from FileMaker Pro that it won't work?