Radio Buttons performs Script

[AudioFreak]

Hello all,

I'm sure this is easy it's just not my day. I have a field set as a radio button. What I would like is if the user selects NO it will perform a script that populates 4 different fields. The script works fine. What I tried was placing a button behind NO in the field so that when no is selected it will run the script. I send the button backward and it goes behind the field. I bring the button forward and you cant tell if the Radio button is selected but it performs the script. What am I missing? Thanks for the assistance.

Michael

[kenneth2k1]

The ghetto way to do it is to have a separate script for each item. Make a transparent button that sets the field to that specific item. The script would also have all of the other steps you need. Make sure that you don't allow entry into the field, and place the button over each item. One more thing to keep in mind is a step that goes to another field, so that after the set field, the selected field is not the radio button field.

Another way is to use a plug-in that can call scripts upon exiting a field.

Ken

[AudioFreak]

That is as "ghetto" as setting the text name next to the field to perform the script. I was hoping there would be a more elegant way to do this. Maybe with the next version of Filemaker. Thanks

Michael

[-Queue-]

Put the button in front of the field, make sure it's transparent, and don't allow entry into the field formatted as radio buttons.

[AudioFreak]

Queue,

I would like to do this that way but there are multiple choices in the field. Only if NO is selected then it will perform the script. I'm trying to think of a way around this as this is what the boss wants. May not get her way this time. It looks like one of the "ghetto" solutions will have to do.

Michael

[AudioFreak]

Queue,

Where are you located in Cali? I work in the Smelley Fly ridden city of Chino.

Michael

[-Queue-]

How many options are available for the field?

I be in FrrresssNOOOOO!

Well, Clovis at work, actually. Fresno when I cross the street and go home.

[AudioFreak]

Queue,

There are only 2 options. Basicaly if a customer sends his unit back in a crappy box we will not return the unit in the same crappy box(some units cost as much as $8000) so he gets charged for the new box and foam. When the comes in the receiving guy checks yes or no. This form is printed and sent back to the customer so he needs to see no selected in the field and Qty of "1" and "Foam and box charge" and "$30.00" are set to the correct fields. You have some other thoughts on this?

Fresno? Your a little to far for us to JAM heh. Too bad.....we could use some of the gear where I work to record our session.

Michael

[-Queue-]

Hmm. You said there were multiple choices in the field. Did you only mean two? If so, then it's easy enough to set up a script to substitute the existing selection for the other. Choose( TextToNum( field ), "Yes", "No" ) will work for you, and you only need one button on the field.

I'll let you know when I make my way down to OC next. Maybe we can schedule a jam.

[AudioFreak]

I will give that a try. Thanks for the time.

A jam session would be fun.

Michael

[Ugo DI LUCA]

jammin'

Where, when ?

Yep the Choose would even be "neater" if you change your standard Radio button to some container field. A Toggle script would be sufficient + the SetField for your 1 thing.

Have a look at this file for the container tip.

Now, if you had more than two choices, a workaround would have consisted in defining 2 value lists.

One with the "No" only

One with all other values.

And to reset any control on field in the Define Field Menu.

A display trick would therefore be used to set those radio buttons as if they were from the same field, while the "No" part would have been set as a button with not allow entry, and the other would have allowed entry into field.

Then, the scripted part (for your "No" option) would have done somehow the following

If [Patterncount(MenuButtons, "No")>0]

SetField [MenuButons, Substitute(MenuButtons, "