zxcvbob wrote:
> isw wrote:
>> In article >,
>> Dave S > wrote:
>>
>>> Notepad
>>
>> There are a lot of problems trying to use any sort of text editor or
>> word processor for recipes.
>>
>> For entering single recipes, they're OK; where they fail (as do
>> "standard" database programs) is handling a recipe collection,
>> especially one of any size.
>>
>> None of them understand the difference between an ingredient and a
>> procedure. None can handle categories well (cheese, beans, Italian,
>> main dish, appetizer, starch, crockpot, ...). None can do effective
>> searches through a collection of recipes. None understand linking
>> recipes (every recipe that calls for, say, Bernaise sauce linking to
>> the Bernaise recipe), which is also useful in reverse: "I really want
>> some Bernaise sauce; what can I pour it over?" And on and on.
>>
>> Isaac
>
>
> I use my *brain* to handle the understanding part. I'm not being
> sarcastic. The recipe files just hold the detailed information in a
> sharable format. The categories are handled by having 5 or 6
> directories (folders). If a recipe fits in more than one category, you
> can create symbolic links (shortcuts).
>
> Bob
>

I have 39 cookbooks in my Mastercook collection. You can put as many
catagories in each cookbook as you wish and you can put a recipe into as
many categories as you wish. You can also add "cuisine"

I can have a recipe for a veggie casserole that will be under the
casserole and one-dish meal, vegetarian, vegetable, pasta and rice, and
then in cuisine such as Italian or Mexican. I even have a cuisine called
pot luck so I can go there and find pot luck suitable recipes if I want.

--
Janet Wilder
Way-the-heck-south Texas
Spelling doesn't count. Cooking does.