All this talk about DataBases

[Chipp Walters]

For small databases, (like the simple Address Book sample), the
embedded database/biz logic works pretty well.

But for larger projects, and especially projects where you need to be
able to provide support to many users, it's imperative to separate the
business logic from the data. You can still do this using RunRev
stacks, just have the stacks hold only the data, and you move it from
card to main interface stack. Once this separation is achieved, it's
much simpler to choose whatever format you would like to store your
data in, be it cards, custom props, text file, SQL server, MySQL,
altSQLite, Valentina, etc.

One huge advantage of using an external databsase like SQLite is the
ability to store data outside of RAM. HyperCard used to use a non-RAM
based design, but Rev stores everything in RAM. So, if you have an
address book which has 100,000 records in a single stack, then all the
records would need to be stored in RAM simultaneously, creating
performance problems.

Plus, there are a number of huge advantages of using real databases.
Concurrent users, real transaction management, stored procs, etc..