ACCESS Database differentiation approaches... need a computer guru here?

Question

Differentiate btwn a file processing system approach and the database approach. I'm trying to figure out the key differences.

Answer 1

A database not only keeps your data, it keeps data about the data. In other words, the definition of all the tables (files) and columns (fields) are kept inside the database in other tables and fields - it's self-defining.
A file processing system relies on logic (programs) outside the file structure to define/identify what files are involved, what fields are in the files, and what are the relationships between the files/fields.

Also, because the database architecture is encapsulated, it lends itself better to operate in client-server mode than a file processing system.

The interesting thing about Access (specifically, the MDB file itself using the Microsoft Jet Engine), is it's really a cross between the two. While it does maintain information about the tables and columns internally and "emulates" a relational database, Microsoft Access doe not run in client-server mode - in other words, your Access application must have read/write access to the Access MDB file to use the data in it - it's definitely not client-server.