Yes, this can be done, but since you are mimicking the behavior of a set of check boxes, why not just use check boxes instead of buttons?
I have a checkbox set-up already but would prefer to have a single word recorded in the value field, rather than having each word selected being recorded in the value field. If there is a way of separating the word in a value field then the checkbox would be an option but I don't know how to write the necessary script.
Can you explain what you are trying to do in more detail?
That description doesn't seem to make sense. A check box interface normally implies that the user may select multiple values. If the user is only permitted to select a single value from the list, a radio button format makes more sense.
I Know little or nothing about databases. I am trying to match an employee who may have multiple skills with a job enquiry. I have the employees personal information recorded within the database and I am now looking to record individual skill sets (some may have a single skill while others have different multiple skills). I would then like the skills information to be checked against the skills requested on the job enquiry to see if any of the employees match those skills.
The checkbox meets the recording needs, but I don't know how to write the script to use the information held within the value field, i.e how to interrogate the information held within the value field holding the employee skills and the requested skill asked for in the job enquiry.
Hope this makes more sense
That one's right on the balance point between buttons controlling records in a join table and using a single checkbox formatted field for listing skills. I'd probably use the first option, but the second is easier to implement--it's just harder to work with for some types of reporting and can be less flexible when working with very different size lists of skill sets.
To check to see if a value is selected in a checkbox field, Not Isempty ( Filtervalues ( YourTable::YourCheckboxField ; "Value" ) ), will return True if "Value" is selected in the check box field.
In a relationship:
Applicant::SkillsetCheckBoxField = Position::SkillSetCheckBoxField
will form a valid relationhip link if any one value selected in the first check box field is also selected in the check box field in Position.
But a relationship like this:
Applicant::__pkApplicantID = Skills::_fkApplicantID
is more flexible.
A portal to Skills on your Applicant layout can be used to list all skills selected for that applicant.
Or you can use your button idea to create/delete records in that Skills table with conditional formatting on the buttons used to show which skills are and are not selected. This conditional formatting can actually make your buttons look and function exactly like check boxes.
See the Checkboxes layout in this demo file: https://www.dropbox.com/s/oyir7cs0yxmbn6i/ManyToManywDemoWExtras.fp7
If you are using FileMaker 12, open this file from the File menu to produce a copy that is formatted to the FilelMaker 12 file format.
I think it will take me a while to sift my way through all the data. Great response, thanks again.