[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Databases on the Apple
- Subject: Re: Databases on the Apple
- From: Hugh Hood <hughhood@earthlink.net>
- Date: Tue, 06 Oct 2009 22:44:22 -0500
- Newsgroups: comp.sys.apple2
- References: <dog_cow-1254514450@macgui.com>
- Thread-index: AcpHAHThs5xEKLLzEd62sgAFAuvodg==
- Thread-topic: Databases on the Apple
- User-agent: Microsoft-Entourage/11.4.0.080122
- Xref: g2news2.google.com comp.sys.apple2:13971
I'll second what Robert Boucher and Warren Ernst mentioned about the strong
capabilities of both the TimeOut-enhanced AppleWorks database module and
also the built-in strengths of the AppleWorks 5.1 database.
Many thought that in AppleWorks versions 2 and 3 the database was the least
robust of the three modules, (the spreadsheet and the word processor being
the other two). While it was easy to use and lightning quick, the bare bones
database program lacked what some would term 'heavyweight' features,
particularly with regard to its report generating capabilities.
TimeOut ReportWriter (by Dan Verkade) attempted to address one of these
shortcomings in AppleWorks 2 and AppleWorks 3 by allowing one to construct
complex reports that could draw information (lookups by key and lookups by
record) from up to 11 different word processor, database and spreadsheet
files (and up to 250 database categories/fields), and included a whole slew
of calculated math and string functions.
Moreover, when the report was generated, it had the capability to 'post'
updated information back into other files. It was billed as a 'Relational'
report generator for AppleWorks.
Like others at the time, I felt ReportWriter had its greatest potential for
use with a database file in order to pull in information from spreadsheet
files, particularly since the database could only handle 30 categories
(later increased to 60) per record, while the Spreadsheet had no such
limitation. This is especially important when generating multi-line invoices
with many items. In this model, the database holds the 'header' and
'summary' information, with the companion spreadsheet file containing all
the line item detail.
Unfortunately, as the power users discovered, ReportWriter had a serious bug
(that was never corrected) when drawing information from spreadsheet files,
so it was an imperfect tool. It _is_ good for other purposes, though.
{Luckily, by combining the power of UltraMacros and the word processor's
mail merge function, one could get around ReportWriter's spreadsheet import
limitations, albeit without using ReportWriter}.
When AppleWorks 4 (and then 5) hit the market, the database module had
changed significantly. Randy Brandt (along with Dan Verkade) made a
concerted effort to improve the database, and to add 'relational' type
features to it, along with many, many other additions, which are too
numerous to list in this post.
The relational type features included are 'Glossaries', 'Imports',
'Exports', and 'Lookup Lists'.
These are all very clearly explained in the 'AppleWorks 4 Reference Manual',
and as I have stated in prior posts, it is a real shame that this 500 page
manual (along with the 100 page AppleWorks 5 Delta Manual) is in limbo and
unavailable on the 'net.
BTW, ReportWriter works with AppleWorks 5.1, but it still has the
aforementioned bug.
Finally, as Matt mentioned, DB Master _Professional_ (not to be confused
with the non-relational DB Master Version 5) is an incredibly powerful
relational database manager. It doesn't have AppleWorks' user interface or
ease of use, but it offers things that AppleWorks doesn't, such as 200
fields per record, and 250 characters per field. The documentation alone is
over 700 pages.
Barney Stone of Stone Edge Technologies <http://www.stoneedge.com> put a
_ton_ of effort into writing and marketing it in the late '80s and early
'90s, and finally threw in the towel in disgust after Apple continually
refused to market the Apple II as a serious small business/productivity
machine, but rather instead as a K-12 educational computer.
Moreover, Stone Edge offered the 'BASIC Programmers Pak', which allowed one
to access DB Master files from BASIC programs (using the '&' command). You
could find, add and delete records, and to examine or change their contents,
all from BASIC. [Wouldn't it be nice to have this feature for AppleWorks?]
Also offered was the Developer's Pak & Run-Time Program, which allowed you
to create 'custom' DB Master applications that others could use. Neat stuff
for the Apple II.
I bought all these programs before Barney called it quits. Unfortunately for
me, even 200 fields/record wasn't enough for my invoicing program.
Thank goodness for AppleWorks 5.1 and UltraMacros, though. By linking the
SS, DB and WP together with UltraMacros, you can do just about anything you
want.
Anyway, Barney Stone (Stone Edge) now develops and sells e-commerce
software. I'll bet if you _really_ want to try a copy of DB Master
Professional, he'll sell you one, for a price. <grin>
Hugh Hood...
in article dog_cow-1254514450@macgui.com, D Finnigan at dog_cow@macgui.com
wrote on 10/2/09 3:14 PM:
> I was wondering if any interesting database programs were made for the Apple
> II, such as relational databases.