The document discusses a pet database with tables for pets and owners. The pet table has a primary key of ID and includes fields for pet type, name, and date. An input mask validates the postcode field. The tables contain relational data and have a one-to-many relationship where one owner can have multiple pets. To prevent duplicate data and improve efficiency, the data was split into two tables linked by a foreign key. Forms allow adding, viewing and deleting data and make the database easier to use for people with basic computer skills.

1. Databases
The table is the “pet database” and the individual sections are
field’s e.g. pet type & pet name. The primary key is a unique
identifier that is the field “ID” they can be crucial for the table.
An input mask is a validation that is pre-set for different things,
in this table “postcode” is being used.
The data we are using is relational that means they are
different pieces of data that are relevant together.
An entity is a “thing” that we want to store data about.
In the table I have added date into it.
A problem is that data in the table is being duplicated and is inefficient. To solve this problem we are going to make
two tables.
For this we have created a relationship, this is using “Forced
Referential Integrity” so that information that isn’t added to
one table isn’t in the other, this is creating a foreign key for
owner ID in pet table. Also this is a one to many relationships
meaning the owner can have more than one pet.
The form is used for adding, viewing and deleting
data. Also it’s easier for people with basic ICT
skills.
There is a form to add information to the table.
Corey scothern
The 1st
entity is about the owner
and 2nd
about the pet.

2. Queries to show pets aged over 12 and that are owned by Dave LeRave.
I have used a report to show
the information of pets aged
over 12. It is used to show the
wanted information in a better
format for people that want to
see the information.
Corey scothern