I was looking for the possibility for generating a dynamic value list based on a checkbox set.
I came up with a solution which is attached. Question is: "It seems to be working but is it a correct solution?"
It's a common feature in many FileMaker solutions. The check box format produces a list of selected values separated by returns. When used as a match field in a relationship, you get an "OR" type match where a record on the other side of the relationship will match if any one of the selected values matches.
As long as that "or" matching logic works for what you need, then you should be good.
BTW, there are many ways to get a returns separated list in a field besides a check box format. Since all of them produce the same type of return separated list of values, you get the same result if used as a match field in a relationship. In addition, that return separated list is kind of a "limited join table all in one field" method that supports many to many relationship designs. Sometimes this is a good thing and sometimes the greater flexibility possible when you use an actual join table is the better option.
If it meets your needs and doesn't fail to work for you, then it's correct is it not?
I would agree. But is the relation conclusive? I mean the criterium field in source matching a "checkboxed" criteria list field in destination?
Thanks for this unambiguous answer.
Retrieving data ...