That is actually pretty simple. Think about storing People and numerous phone numbers for a single person. So that tells you that you will need at least three tables. The one in the middle is called an "associative" table

I am assuming that you cannot have duplicate numbers in either table. So I am going to use a PRI Key in each table. So you will end up having a one-to-many relationship. And you will be able to add or remove as many numbers in the child table as you like

ONe Table

Table1

RowID int PRI KEY

NumericID int

Many Table

Table2

RowID int PRI KEY

NumericID int

Associative Table

Table1RowID int

Table2RowID int

You can build on it form there. you can add a column to indicate whether to show the row or not. etc....

The associative table will contain the PRI Keys from both tables and those will become a composite key. Creating the constraint that will not allow a duplicate row.

Andrew SQLDBA