If he does then my sketchy design was enough to nudge him in the right direction. If he doesn't, then he now knows he needs to learn about keys and field types and has some specific words he can look up in books and help files.
In either case, I gave a reasonable answer to a simple problem, and so have earned my boy scout badge for the day. Heck, I may even deserve a cookie! -- R.B. Davidson On Jan 27, 9:15 am, KeidrickP <[email protected]> wrote: > RB, > do you think he will know the said "datatypes" given his limited knowledge? > > > > On Tue, Jan 27, 2009 at 9:01 AM, rbdavidson <[email protected]> wrote: > > > 1 Table for Recipes, with unique key, preferably autonumber. Include > > memo or a long varchar field for writing out the recipe (i.e. "Mix in > > eggs and flour and put in oven at 350 for 2 hours.") > > > 1 Table for Ingrediants, again unique key, preferably autonumber > > > Cross-reference table that has foriegn keys to both Recipes and > > Ingrediants by their unique keys. Include addtional fields to specify > > measurement units (TSP, TBSP, Cups, etc..) and quantity (1, 2, 3,...) > > > -- R.B. Davidson > > > On Jan 26, 10:42 am, 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- Hide quoted text - > > - Show quoted text -
