examine the construction of the table and you'll find that each column of the table corresponds to a specific employee characteristic (or attribute in database terms). Each row corresponds to one particular employee and contains his or her information. That's all there is to it! If it helps, think of each one of these tables as a spreadsheet-style listing of information. In the previous section, we learned how tables allow us to create the framework for storing information in a database. Obviously, a database that only stored information would be useless -- we need methods to retrieve information as well. If you simply want to recall the information stored in a table, Microsoft Access allows you to open the table and scroll through the records contained within it. However, the real power of a database lies in its capabilities to answer more complex requests, or queries.
Imagine that your organization requires a simple method to create a list of those products that are currently selling above their average price. If you simply retrieved the product information table, fulfilling this task would require a large amount of sorting through data and performing calculations by hand. Additionally, you can instruct the database to only list the name and unit price of the item. Sample output is shown [stop]
user-friendly forms interface that allows users to enter information in a graphical form and have that information transparently passed to the database. The figure below provides an example of the form method of data entry. This method is less intimidating for the data entry operator but requires a little more work on the part of the database administrator. [forms. I like forms. I wonder what that means about a person, tables vs. forms.]
Jose Gonzalez – Heartbeats
Goton Project – Queremos Paz
Regina Spektor - Samson
Imogen Heap – Let Go (solo piano) [best in show]
