using 2 columns in the product options table, one for size and another for color, then using two manage relational table behaviors is not the correct way to accomplish this.
for multiple option types, the database structure would be:
optiongroups:
optionGroupID - Primary key
optionGroupName
example:
|---------------|-----------------|
| optionGroupID | optionGroupName |
|---------------|-----------------|
| 1 | Color |
|---------------|-----------------|
| 2 | Size |
|---------------|-----------------|
options:
optionID - Primary Key
optionGroupID - Relates to optiongroups.optionGroupID
optionName
example:
|----------|---------------|------------|
| optionID | optionGroupID | optionName |
|----------|---------------|------------|
| 1 | 1 | Red |
|----------|---------------|------------|
| 2 | 1 | Yellow |
|----------|---------------|------------|
| 3 | 1 | Blue |
|----------|---------------|------------|
| 4 | 1 | Green |
|----------|---------------|------------|
| 5 | 2 | Small |
|----------|---------------|------------|
| 6 | 2 | Medium |
|----------|---------------|------------|
| 7 | 2 | Large |
|----------|---------------|------------|
in the product options you only have one option column to use in the manage relational table behavior.
in your page, use one recordset to return the options, and one repeat region, set the recordset to order by optionGroupID, then you can add an if statement to change the label to Size if the optionGroupID = 2