just as a starting point, place a duplicate simple Edit Box field next to your matching checkbox field. You'll see that as you check and un-check the boxes, you end up with a ¶-separated list. You can use this list in many ways, including matching child records based on all checked choices.
A few other observations:
If you enter find mode and click a check box, you'll find all records that have at least that value selected. So simple straight forward "finds" in FileMaker can work with check boxes without problem.
But if you find that you need to produce statistical or summary reports based on multiple values entered into a single field, that reporting task isn't so simple. In such cases not only do separate fields with single check box values easier, you may find that setting up an interface that creates individual related records--one record to a value make for easier and more flexible reporting.
If that's an option you need to consider, it's possible to set up an interface that looks like a single field with multiple check boxes, but the user is actually clicking buttons that perform a script that creates or deletes a related record when the value is selected or deselected.
Being new to this platform and not having much code experience (other than markup stuff) I haven't delved into FMP scripting yet. Is there a quick way to get a script to input on check box and how would the performance be on a hosted/FM Go client environment?
1 of 1 people found this helpful
In a script, you would use the Set Field script step and the List function to populate your checkbox field.