I think someone mentioned this analogy but, think of a flat file
database as a single box of index cards. You can sort them, you can
search through them, but there's a lot of duplicated information. This
is fine if you only have a few things to worry about. To use Johannes'
example, say you store the name and address of the person who's
borrowing a particular set of parts. If her address changes, you'll
have to change each card that the borrower is associated with.
A relational database could be described as numerous boxes of index
cards, sitting on a desk. You'd have a box of cards for borrowers, a
box of cards for the scores, and maybe even a box for the parts. You
then have a spot on each card to "relate" the borrower to a part. For
example, say I'm borrower #10110. Instead of entering all my
information on each card I borrow, you simply write 10110. If I move,
you only change card 10110 in the box of borrower cards.
On Aug 19, 2008, at 10:09 PM, John Howell wrote:
Could we define our terms for the non-experts here? What the heck
is a"flat database," and why do you say (in another message) that
FMP is one when David says it is something else?
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
