This is a common scenario... 1 Class can have many Students. 1 Book can have many Authors. .. 1 Recipe can have many Ingredients.
It's called a 1-Many relationship. I suggest you read up on relationships in databases... there are entire books on the subject. On Jan 26, 9:42 pm, BrianP <[email protected]> wrote: > Hello, > > I'm new to developing .net apps and database designing, so naturally I > have a question. > > A little background of what I want to do ... I want to have a table > containing food ingredient information (Names, cost/unit of measure, > etc.), and another table containing recipes. Each recipe will > reference a variable number of ingredients. > > What's the best way to go about storing this info in a database? I was > initially thinking a table for ingredients and a table for recipes, > but since the recipes will reference a variable number of ingredients, > that presented a problem to me with my limited knowledge of database > design. > > Thanks in advance, > Brian
