Yes, and only two fields would be common. The SetID and the Rule Type, or description of the rule. The SetID should never change and changing the description field should be simple as they will all share the same SetID. I think that sounds reasonable.

>>The more I think about this, I could have just one table. A grid could be used to filter to only show records belonging to the same set. Changes that are made would be made to the table.
>
>The one table would be the "detail table", then. This can be done, but then, in theory, any update you do to the "parent" information (the part that repeats is the same for the different details) would have to be updated to multiple record.
>
>A parent-child structure (i.e., seperate parent-child tables) is recommended for cases such as:
>

Invoices, with many details per invoice
>

Students who register in several subjects
>
>etc., i.e., every time you might feel tempted to save multiple pieces of information in a single record.