1 of 1 people found this helpful
The complicated rules that you have make me wonder if this should all be input into a single field or not. To me, there's nothing in your interface design to guide the user in what selections may be made and which may not be made. With the current design you either set up an "auto-correct" scheme where choices made by the user mysteriously change into a combination that is permitted, or you let them make a wrong choice and pop up an error message requiring them to make a correction. Neither seems ideal here.
Maybe making this list of choices a button bar (or group of buttons in an older version of FileMaker) with conditional formatting to change color or Hide Object When making icons visible to both show which values are currently selected and which may be selected given the current selections.
I think your second option makes the most sense. And would be the easiest to accomplish.
I've been spending time trying to write script trigger of options, but that is exhausting in itself.
How about a radio button with the choices as:
Drawings, Locations, Message Schedule
Locations, Message Schedule
Drawings, LOC & MS
LOC & MS
Isn't checking both
the SAME as checking
LOC & MS ?
Why even HAVE that option? Without it, you just have a standard checkbox field situation.
Am I missing something?
It's not the same for my purpose.
What the script is doing is creating cover sheets.
Drawings creates 1 sheet
Location Creates 1 sheet
Message Schedule Creates 1 sheet
LOC & MS creates 1 sheet
Sometimes 3 packets with 3 different covers are needed. Sometimes its okay to combine the info of Location and Message into 1 packet based on the client.
I just don't want radio.... I like the square and checkbox look (call me crazy-- I'm more designer than "coder")