+4  A: 

I'm not sure I understand your exact scenario, but to create a many-to-many relationship, you simply create a "relationship table", in which you store id's for the two records you want to link.

Example:

Products
********
ProductID (PK)
Price

Retailers
*********
RetailerID (PK)
Name

ProductRetailerRelationships
****************************
ProductID
RetailerID
Tomas Lycken
Darnit! Another person sumits the right answer right as I start typing!
Pulsehead
it is another database to maintain... is the checkbox option possible ?... but i totally understand you answer, and it work !
marc-andre menard
Also known as a cross-reference table or xref table for short.
Steve Wortham
It's technically not another *database* to maintain - just another *table* in the same DB. This technique is very common, and is usually one of the first recommendations when talking about *normalizing* databases - that is, making sure that each piece of information is only saved in one place. You *can* do what you want with checkboxes, but you will have to save the same data in several places, thus making it much harder to make sure that you don't have conflicting data.
Tomas Lycken
Another question, is it still pertinent to have the relationship (foreing key) beetween product and format, if i will go with the join database (table)
marc-andre menard
This layout is only for *many*-to-*many* relationships - if one product can only be of one format, your current approach is good enough. However, if one product row should be able to correspond to several formats, you probably want to implement a `ProductFormatRelationships` table as well.
Tomas Lycken
A: 

A many-to-many relationship is almost always modeled using an intermediate table. For your example,

Product
--------
prod_numero
...

Size
--------
size_numero
...

Product_Size
--------
prod_numero
size_numero
...

The Size table would contain particular sizes (say, 10 liter) and the Product_Size table creates a Product and Size pairing.

Adam Robinson
A: 

You Will need an Intermediary, or "Join" Table

ProductSizes
.......................
ProductID
SizeID

One record for each product-size combination

Neil N
A: 
marc-andre menard
I start to think, maybe to go with a xml structure... But i can remember i have read somewhere : Once upon a time, a programmer have a problem, then he use xml, now he have two problem !...
marc-andre menard