A database is a collection of data that you want to manage, rearrange, and add to later. It is a good program to use to manage lists that are not entirely numbers, such as addresses and phone numbers, inventories, and membership rosters. With a database you could sort the data by name or city or postal code or by any individual item of information recorded. You can create forms to enter or update or just display the data. You can create reports that show just the data you are interested in, like members who owe dues.
Both spreadsheets and databases can be used to handle much the same information, but each is optimized to handle a different type most efficiently. The larger the number of records, the more important the differences are.
Examples of databases: MS Access, dBase, FoxPro, Paradox, Approach, Oracle, Open Office Base.
|A flat database||contains files||which contain records||which contain fields|
A relational database contains tables which are linked together. Each table contains records which
A query can filter your records to show just the ones that meet certain criteria or to arrange them in a particular order.
The earliest and simplest databases are flat databases.
A flat database may still be all you need for your purpose.
A text database is a plain text file where the fields are separated by a particular character like a vertical bar | or a comma , or a semi-colon ; . The example below puts a vertical bar between each field. The first record shows the names of the fields.
A text database is hard to read in this raw form. A database program can show each record separately in a more readable display. It is hard to create a report that contains just the parts you want to see.
A spreadsheet can work as a flat database. Each field is in a separate column and each row is a single record. The example below shows how quickly a record gets wider than the screen. You cannot use two rows for one record.
Microsoft Access and Oracle and other relational databases are more advanced and more efficient. This kind of database uses a set of tables which are linked together. Using a well-designed relational database can greatly reduce the amount of data you must enter each time you add a record. For large numbers of records, a relational database can search through the records faster.
Below is an illustration of the tables in a small database that records information about insurance agents and policy holders. This particular insurance office works with several different insurance companies. There are 7 tables in the database. The lines show which fields in each table are the same. These link the tables together.
Each agent can be licensed with several different companies and in several different states. In a flat database you would have to have a record for each agent for every company and state he is licensed with, repeating the agent info for each record. If the agent moved to a new house, you would have many records to update with his new address. Argh! Too much typing!! With a relational database, there will be only one place to update.
You can design a form so that you can do this all in one spot! This is much easier than repeating so much information for each record as you would do in a flat database. The images below show the two screens for the Agent Info Form. This form can be used for entering new agents as well as for displaying the current ones.
You often want to look at just part of the data in a database. You can reorder or filter your data using Structural Query Language (SQL). You might want a list of people who have a particular postal code, for example. Happily there are visual methods you can use to create your query, like the example below from MS Access. You can drag the fields from the list at the top and drop them in the columns at the bottom. You can add sorting orders or criteria, like picking a particular postal code. The query below brings together the fields from the Agent Info table that are needed for mailing labels.
The actual SQL code for this query looks a lot different from the Design view above! No wonder a drag-and-drop method was created!
For a full set of lessons on databases using MS Access, go to: Working with Databases