If a checkbox isn't attached to a field, then where would its status (checked/unchecked) be kept?
I believe that the correct solution for a situation where each entry can have an unknown number of item is to place the items in a related table as individual records .
Okay, as I said, I'm just use Filemaker for personal, casual use, so bear with me here. Are you talking about creating a separate file, linked to my main somehow, that had the individual variable-quantity records within it? But would that be able to keep in sync with the main file then, and each individual record in there? If that's the case, and it's possible, and will allow me to link it in as I'm looking for, that'd be great, and i can start researching how that works.
But basically, what I'm looking for is something for a game, where I have one Record, and it has a player's Name, Stats, what have you, and then also section for Skills. Each player record will have a different number of skills, and they will likely all be different from one player to another. An then I have to have a way of showing what "Rank" each Skill is at (and I was hoping for something a little more professional-looking than simply adding text at the end of each Skill name with the associated Rank).
Hence, I was hoping the program could somehow set up purely visual markers of some sort (like a radio button or three) that I could set up an undifferentiated group of them next to each line of a text box, and just manually enter the skills and then toggle the radio buttons for each skill as needed, since they would never be used in any sort of calculation or the like.
Are you talking about creating a separate file, linked to my main somehow, that had the individual variable-quantity records within it?
Not necessarily (unless you are using version 6 or lower). Starting with version 7, you can have multiple tables in the same file.
But would that be able to keep in sync with the main file then, and each individual record in there?
Yes, through a relationship between the tables. In your example, each player would be assigned a unique PlayerID (auto-entered serial number), and each record in the Skills table would have a corresponding PlayerID value linking it to the parent record in the Players table.
You can view each player's skills in a portal to Skills, placed on a layout of Players - even create them directly by typing into portal (provided you set the relationship to allow this).