12
DATABASE EVIDENCE Zosia Staniaszek

DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

Embed Size (px)

Citation preview

Page 1: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

DATABASE EVIDENCEZosia Staniaszek

Page 2: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

FIELD NAMES AND DATA TYPES

I switched to design view to enter the field names and change the data types.

I entered the field names as shown in the list from the

website.

For ‘Name of Species’ I made sure that it was a primary key so that each record is unique. I also checked that it was indexed in the ‘field properties box.

I kept ‘Group’, ‘Location’, ‘Status’ and ‘Threat’ as text because they include letters and words.

For ‘Weblink’, I changed the data type to hyperlink because it is a web address and so that the website can be easily accessed.

I changed ‘Adoption Cost’ to currency because it is numbers and entered in pounds.

Page 3: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

FIELD SIZE

For ‘Adoption Cost’ I checked that it was in pounds and then changed the number of decimal places to two, as specified on the website.

I changed field size of the ‘Threat’ field to 1 because it is either C, L, H or P.

I changed the field sizes because it saves space when saving the database and makes it quicker to search.

I changed the field size of the ‘Group’ field to 18 because this is the longest possible choice.

I changed the ‘Location’ field size to 30 to save space.

I changed the field size of ‘Status’ to 6 because it is coded and the longest code is 6 letters.

Page 4: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

VALIDATION RULES - GROUPI created the validation rules for the ‘Group’ field using the lookup wizard.

I entered the groups found on the website in the lookup wizard and also the validation rule so that no incorrect data can be entered, and it options appear as a drop-down list.

I tested the validation rule by going into datasheet view and entering a random word. The error message came up, showing that the rule was successful.

Page 5: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

VALIDATION RULES - STATUSI created the validation rules for the ‘Status’ field using the lookup wizard.

I entered the different codes found on the website so that it would

come up as a drop down box and then also entered a validation rule so that only these items could be

added.

I made sure that the drop down box worked and tested the validation rule by going into datasheet view and entering a random code. The error message came up, showing that the rule was successful.

Page 6: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

VALIDATION RULES - THREATI created the validation rules for the ‘Threat’ field using the lookup wizard.

I entered the different codes found on the website and

created a validation rule and validation text which should come up if a value not in the

rule is entered.

I tested the validation rule by going into datasheet view and entering a random letter. The error message came up, showing that the rule was successful.

Page 7: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

IMPORTING DATA

I imported the data using the text file from the website and all of the data was imported successfully, none of the records were rejected. There were 174 records altogether.

Page 8: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

DATA ENTRY FORM

I put in the wildcare logo and a relevant title for the form.

I made sure that all of the validated rules had drop down boxes to make it user friendly and to prevent invalid data from being entered.

I included a key so that the users know what the codes stand for.

I also added an ‘Add New

Species’ button so that new records can

easily be imported.

Page 9: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

Feedback for form from test buddy:

‘It is very clearly structured. There is a good colour scheme which adds to the professionalism of the form. It also has

a button to be user friendly, and the drop down boxes to save time and

errors while entering data. You could change the form to match with the

whole project for extra consistency.’

FEEDBACK / TESTING

Feedback for final form from test buddy: ‘It is very good, easy to add new records and matches the whole of the project.’ I tested the button for adding

new species, and a blank form appears so it works properly.

I tested the validation rules by entering incorrect records into the validated fields, and the validation rules worked because an error box appeared. Also, I tested each of the drop down boxes.

Page 10: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

ADDING NEW RECORDS - BISON

I added this new record to my database using the data entry form to show that it worked. I found the information from websites recorded in my sources table.

I used this to find out the threat: Hunting.They are not

endangered, so I entered the status as ‘At Risk’, so Blue.

Source: http://www.npca.org/protecting-our-parks/wildlife_facts/bison.html

Page 11: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

ADDING NEW RECORDS - BABOON

I added this new record to my database using the data entry form to show that it worked. I found the information from websites recorded in my sources table.

I put the status threat as ‘orange’, because this source says that they are endangered.

I chose to put hunting, because loss of habitat is also due to humans.

Source: http://wiki.answers.com/Q/Why_are_baboons_an_endangered_species

Page 12: DATABASE EVIDENCE Zosia Staniaszek. FIELD NAMES AND DATA TYPES I switched to design view to enter the field names and change the data types. I entered

ADDING NEW RECORDS – MEXICAN WOLF

I added this new record to my database using the data entry form to show that it worked. I found the information from websites recorded in my sources table.

I put ‘Critically Endangered’ as the status.

This paragraph shows that the wolf has become critically endangered because of hunting.

Source: http://en.wikipedia.org/wiki/Mexican_wolf