Shouldn't be a problem, but the approach depends on how you would like to
access the data later.
Will you be storing the methods/steps as well?
Will you need to link it (loosely) to something else - say procurement and
sales? Or it's just recipes.
Because it's quite different if you later want to find out:
We sold X number of various products.
Based on the recipes we should have used Y raw materials.
Compare this with what we're buying. etc etc.
vs.
I just want to look up recipes given some keywords.
Cheerio,
Link.
At 09:06 AM 02-06-2000 -0700, moebius@ip-solutions.net wrote:
>Hey All,
> I was wondering if anyone had an example of writing a recipe database
>that I could take a look at. I am by no means a db programmer but I would
>like to give it a shot. What i am trying to do is somthing like:
>Pie $3.70
> 1/4 cup sugar @ $1.10
> 1 pie crust @ $.60
> 3 apples @ $2.00
>Any help would be greatly appreciated,
>Thanks,
>
>Harry Hoffman
>Manager - Information Technology
>Restaurants Unlimited Inc.
>206.634.3082 x. 270
>
>
>
>
