I would suggest that you would be better off having a separate table for variations. So you have one table for products which contains a record for products 1,2,3... And another table for each variation of each product. With your example data, you would have three product records and six variation records.
When this is done, you can create a calculation field in the Product table to display the list of variations:
Substitute ( List ( prod_VAR::variation ) ; ¶ ; ", " )
This calculation will show all related variations separated by commas.
In the products portal, you would display two fields - the product number and the variations list.
Yes, making a new table makes perfect sense. The table I currently have is the "variatons" one, so I need to make the "products" table, guess I will have to populate manually?
Also, if the user inputs the data into the "product" table, is it possible to make a button/script to "add variation" so that the new record created in the "variation" table has the same catalogue number as the initial product?
I came to think that probably it is possible to use a variable to copy a filed from one record to a field in a different record and table. Is it correct?