Newbies DMSeb Posted September 16, 2005 Newbies Posted September 16, 2005 I've been trying to use the SetField function to select a radio button based on it's value list with no luck in getting to work. Am I going about it wrong? Any insights would be appreciated. -Thanks
-Queue- Posted September 16, 2005 Posted September 16, 2005 Could you elaborate? Setting a field formatted as a radio button is no different than setting a normal field. Set Field [field; "value"] will work. The only requirement is that "value" be an item in the value list used to format the field.
Newbies DMSeb Posted September 16, 2005 Author Newbies Posted September 16, 2005 See thats what I thought as well but I get the operator error when I set it using the semicolon. The script line looks like: Hardware::ProductType ; "Computer" And "Computer" is defined in a value list that I have created also labled ProductType. However it says that is expecting an operation (eg. +, -, etc) So I switch to good old Hardware::ProductType = "Computer" which is accepted as a forumula but it does not change the radio buttons when performed.
-Queue- Posted September 16, 2005 Posted September 16, 2005 In Set Field [Field; "value"], Field is the target field; it does not go in the calculation. The semicolon separates the two parameters; it is not entered in the calculation either. The only thing entered in the calculation is "value". Set Field [Field; "value"] is the way it will appear in ScriptMaker once you have selected the field and entered the value.
Newbies DMSeb Posted September 16, 2005 Author Newbies Posted September 16, 2005 Wow... Thanks so much for clearing that up for me. I can't explain how confused I had been on that one. I've been overcomplicating the whole process. Again thanks so much for your help.
-Queue- Posted September 17, 2005 Posted September 17, 2005 No problem. Forum syntax is often confusing for new FileMaker scripters (to say nothing of ScriptMaker itself). We have mostly settled into presenting steps as they appear in ScriptMaker, to reduce confusion as much as possible. But it doesn't hurt to clarify that every once in a while.
Recommended Posts
This topic is 7010 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now