
open a database and select Reports from the Database pane, then Use Wizard to Create Report, and follow the steps outlined in the Report Wizard. However, this limitation is partially compensated by the fact that reports in Base are quick and easy to create and are displayed and printed in Writer, which gives you tools to improve their layout. The designs of its reports are simple and not overly attractive. Reports are an effort to manipulate database records into a more friendly form, including preparing them for printing or for insertion into a larger document.īy the standards of other databases, such as MySQL or Oracle, Base has a limited report capacity. In fact, to anybody who's not an accountant or a computer geek, reading databases can be downright intimidating. Or, at least, that's the case in Base, regardless of whether you view a database's tables directly or filter them through a query or form. Unless a person is in a habit of regularly getting fuel and having their vehicle serviced, the entries in these tables do not share anything in common.Let's face it, databases are only minimally human-readable. The Fuel and Maintenance tables do not really have a relationship even though they share similar fields: Date, and Odometer. That will be done when the forms are created. Since the Payment Type table only provides a static list, we will not be defining a relationship between the Payment Type table and the fields of the other tables which use the entries of the Payment Type table. The relationship between these fields of those tables and the Payment Type table are also 1:1. (It is designated 1:1.) Other tables also contain fields for the type of payment.

This is a one to one relationship: one field in one table to one entry from the other table. For each field listing the payment type, there is only one entry from the Payment Type table.

The Vacations tables also contains several fields for the type of payment used. Since the Fuel table may have more than one entry per date, this relationship between the Vacations and Fuel tables is one to many. So, we will relate these two tables using the Date fields. Most of these expenses are in the Vacations table, but the fuel we buy is not. When on vacation, we want to enter all of our expenses all at one time each day. Now that the tables have been created, what are the relationships between our tables? This is the time to define them based upon the questions we asked and answered in the beginning.
