That's exactely what it's supposed to do and has ever been since at least FM6.
See the holding-Shift-Key trick for multy-selection as kind of a override-function.
Expected result: as it is √
I strongly disagree. There should be no provision by using a modifier key to override the basic nature of a radio button set. This is a bug.
I hesitate to come here. I am sure that this thread will become a little bit philosopical and passionate. But OK, a little debate on monday morning, is good for the mind, even we are on the wrong section, excuse us Phil...
Dear Rick :
As an experienced developer on FMP, you know well that this behavior is depending of many FileMaker's basis concepts, in french we are saying : "only the Iceberg's edge", and moreover, you have many ways to avoid it by programming.
Anyways, i think we cannot consider as a bug this behavior because it is just expected as is by the developer, even we, the users in this case, strongly desagree it. As sayed on another thread, i think you are more waiting for a boolean Field, not for a simple control style as the "Radio Button" is on FileMaker.
And also, today we ar not still in 1984. You will find many behaviors on actual computing that are unconsistant, like for instance, the ability of choosing many values on a pop-up menu (by pressing shift i think...). But i agree : it is too bad...
PS : Please excuse my english approximative.Edit : Just to notice that it has been also reported here... some hours after :
This has been reported before, but FileMaker does not agree that it's a bug as I recall. You may want to use http://www.filemaker.com/company/contact/feature_request.html to add your voice to others that have requested that this be changed.
Thank you for post.
This behavior has been this way for many years and is as designed. FileMaker's Knowledge Base article, KB 5187 Checkboxes and Radio Buttons - How they Work states:
"You can hold down the shift key while clicking a radio button array to force it (temporarily) to behave as if it were a checkbox array."
If you would like to see a change in this behavior, I would encourage you to enter this as a suggestion into our Feature Requests web form at:
This behavior has been this way for many years
And for many years developers who have encountered this unexpected behavior have complained and asked that it be changed--at least to give us a simple way to prevent it rather than having to use an auto-enter calc on every field where we set up a radio button format.
You can easily get around it by making the field a button that toggles or rotates between values.
For example a yes / no field could be changed to a button that sets that field with the calculation that if it equals yes then set it to no etc and you can include a a deselect too. This can be tied in to other fields too if necessary. So maybe Field A can only be "yes" if Field B is "Blue" for instance.
It's not easy to judge on this. Since this is the way it used to work for the last decades, changing this behavior could cause more damages than benefits. I know there's a lot of objects I'ld have to change if this wouldn't work anymore the way it did in the past.
Since the OP goes back to 2013, I'm confident that easy work arounds are at hand with new features introduced FMP13 and FMP14. A Script trigger OnObjectModify could work this out anyway.
This was reporting a issue 3 years ago. Already have a workaround which is stated in the original post.
Radio button - Wikipedia, the free encyclopedia, I haven't tested , so I do know if anything has changed in FM14, but FM Radio button is not a true radio because it allows more than one selection, which is what the post is about.
The design has not changed in FileMaker Pro 14. You are still allowed to select multiple radio button values using the Shift key. Plus, what hasn't been mentioned in this thread, you have the ability to clear out a field by unselecting the value(s).
Old post that hasn't been an issue. It's just a matter of knowing how it works.