Sounds like one parent with multiple children. Just have a field in the child table that holds a foreign key to the parent.

>The entry cursor I've been talking about is kind of the child. I don't see the need to maintain a physical table for that as everything pertaiing to the rule set can be displayed all at once on the form. The "parent" table would really contain one record per rule, but the form/cursor would create multiple records/rules in the parent table. If that is still confusing, then I'm not sure how to explain it differently.
>
>Ok, if they select checkboxes on Monday and Thursday, then two records would get created in that "parent" table when they save on the form. Did that make sense?
>
>And, there is another form calling the entry form. That one displays the records from the table. Select from that to go to the 2nd form where the entry into the cursor is done. If this is totally wrong from a design standpoint, let me know and perhaps a better overall suggestion.