Relational Database

To create a family reunion database using Microsoft Access, we first need to break down the information currently available to us.
Since the database will hold names and other information on family members attending the reunion, we need to decide on the model type of the database. Family reunion is rather straightforward event with not much complexity to the data, so it will be easier and much more efficient to use Relational Database Model.
Relational Database model is a simple database, which includes Entities, Relationships and Attributes. In our case the Entities are our family members, Relationships are their degree of relation to the database creator and Attributes are going to be their contact information that will allow us to invite them to the reunion and their response to the invitation. Relational model is a much simpler,
As the database will be used to input all relatives that are invited to the reunion, it will also include address, relationship hierarchy to the creator and invitation response. With this information multiple reports can be generated to produce a list of denied or accepted invitations, as well as a report to show any possible food allergies.
Important part of the design method, that is getting the most use in the whole process is the report design. Reports are the bullet points of the database, generated based on one or multiple conditions. The more task specific the repost is, the greater use it will get. In the example with the family reunion, report on accepted or declined invitations can provide exact number of people attending and report on food allergies can help avoid allergic reaction situations and help diversify the menu options. Third step in design method is data design. Consistency in items throughout the database will help with building reports and avoid errors. Same data item name should be used in reports as it is in the