Harrow Fix-IT
Structure Evaluation (20 minutes)
Evaluate your database structure.
You should consider:
How well your database structure minimised data duplication
How well your database structure meets these requirements:
o There are three types of repairs: peripherals, software and hardware
o A record cannot be saved if the repair reported date is in the past
o The customer postcode will not save if it is in the incorrect format
Structure Evaluation
Database Minimising Data Duplication
My database minimises data duplication by using primary keys in the tables, this minimises data
duplication because with primary keys only one record can have a specific ID allocated to it and if
multiple records have the same ID, the duplicates will be deleted. An example of this being
present in my database is with the Customer ID if there are records with the same and it is set to
be the primary key, the duplicates will be deleted and it will only keep the records with unique
ID’s.
Database Meeting the requirements
Three types of repairs
My database only allows three types of repairs to be inputted into the Repair Type field, these are
Peripherals, Software and Hardware. This is achieved by using a lookup wizard
("Peripheral";"Software";"Hardware”) to create a drop down box that lets people choose from the
three options, if something other than these options are inputted then the database will not save.
When testing this in my database I had created the lookup wizard to allow options to be
displayed, so it had passed the test.
Report date being in the past
My database only accepts dates that are between the 27/09/2019 and the current date. This is
achieved by using a validation rule ( >=#27/09/2019# And <=Now() ) that specifies the dates it
should only allow and if a date is inputted that is out of the range of the two dates, it will not
allow the database to save which forces the person inputting the data to change it to a suitable
date. When testing this in my database I had not included a validation rule at first but once I had
tested for that and found it was not there, I added it in and now it works as it should.
Postcode being in the incorrect format
My database only allows postcodes have been inputted in the correct format. This is achieved by
using an input mask ( AA00\ 0AA ) that only allows characters to be inputted in that specific way, if
it is not typed in this format it will prevent the database from saving until the person has changed
it to follow the rules set in place. When testing this in my database I had not added in a format to
make sure it is correct but when I tested it and found it was not working, I implemented it in and
now it works.
Structure Evaluation (20 minutes)
Evaluate your database structure.
You should consider:
How well your database structure minimised data duplication
How well your database structure meets these requirements:
o There are three types of repairs: peripherals, software and hardware
o A record cannot be saved if the repair reported date is in the past
o The customer postcode will not save if it is in the incorrect format
Structure Evaluation
Database Minimising Data Duplication
My database minimises data duplication by using primary keys in the tables, this minimises data
duplication because with primary keys only one record can have a specific ID allocated to it and if
multiple records have the same ID, the duplicates will be deleted. An example of this being
present in my database is with the Customer ID if there are records with the same and it is set to
be the primary key, the duplicates will be deleted and it will only keep the records with unique
ID’s.
Database Meeting the requirements
Three types of repairs
My database only allows three types of repairs to be inputted into the Repair Type field, these are
Peripherals, Software and Hardware. This is achieved by using a lookup wizard
("Peripheral";"Software";"Hardware”) to create a drop down box that lets people choose from the
three options, if something other than these options are inputted then the database will not save.
When testing this in my database I had created the lookup wizard to allow options to be
displayed, so it had passed the test.
Report date being in the past
My database only accepts dates that are between the 27/09/2019 and the current date. This is
achieved by using a validation rule ( >=#27/09/2019# And <=Now() ) that specifies the dates it
should only allow and if a date is inputted that is out of the range of the two dates, it will not
allow the database to save which forces the person inputting the data to change it to a suitable
date. When testing this in my database I had not included a validation rule at first but once I had
tested for that and found it was not there, I added it in and now it works as it should.
Postcode being in the incorrect format
My database only allows postcodes have been inputted in the correct format. This is achieved by
using an input mask ( AA00\ 0AA ) that only allows characters to be inputted in that specific way, if
it is not typed in this format it will prevent the database from saving until the person has changed
it to follow the rules set in place. When testing this in my database I had not added in a format to
make sure it is correct but when I tested it and found it was not working, I implemented it in and
now it works.
