Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!pacbell!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!nsc!voder!apple!dan
From: dan@Apple.COM (Dan Allen)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Database toolkits
Message-ID: <11434@apple.Apple.Com>
Date: 1 Jun 88 20:57:36 GMT
Article-I.D.: apple.11434
References: <17474@glacier.STANFORD.EDU>
Reply-To: dan@apple.UUCP (Dan Allen)
Organization: Apple Computer Inc, Cupertino, CA
Lines: 25

Using the Resource Manager for a database manager is *** NOT RECOMMENDED
**. PERIOD.

The Resource Manager is moderately good at doing what is was designed to
do: handle a few dozen MENUs, DLOGs, CODE segments, etc.  The Resource
Manager was speeded up quite a bit from the 64K ROMs to the 128K ROMs,
but it still is largely a linear critter.  Binary trees and the like are
definitely needed for writing good database stuff, and the Resource
Manager simply doesn't do it.

You may not expect the following recommendation, but depending upon what
your data is, Apple does supply a very nice database tookit for the
Macintosh: HyperCard.  It has **VERY** sophisticated search techniques
and supports text, graphics, and sound quite nicely.  You can use XCMDs,
written in C and/or Pascal, to extend HyperCard.

Now I know that HyperCard is not the answer to many database problems.
It is certainly **NOT** a relational database.  If you are looking for
those kind of database toolkits, then the BTrieve/generic C type stuff
is probably as good a canned stuff as you are going to find.  And I know
very little about those, so I can't help you with them.

Dan Allen
Software Explorer
Apple Computer