Wildcare

1. Wildcare Database Structure and Evidence

2. Entering Data Fields • In order to create my database, I was given a data items list, which told me the field names that I had to enter into it. It also specified how each field should be formatted. I used this list to ensure that I formatted the data fields correctly. For each field, I entered a description in order to aid the user when using the database.

3. Adjusting Field Properties: Data Types • Name of species Because the data items sheet requires all fields to be populated, I went to the ‘General’ section and changed ‘Required’ to ‘Yes’, ‘Allow Zero Length’ to ‘No’ (this makes sure that the database will ask for all the fields to be populated and will not let the field be populated with information that has a length of zero). I also selected ‘Yes (No Duplicates)’ so that no records can be entered twice. I made this field a primary key so that each record’s name is non-adjustable. I changed the field size to 100 to preserve memory.

4. Group This field had to have a validation rule which I created, as well as a validation text which will appear when an incorrect value is entered. I then used a Lookup Wizard to create a drop-down menu. This, however, stopped the validation text from working. I then had to back to my Lookup Wizard and unselect ‘Limit To List’. I also used the same methods as for ‘Name of Species’ to ensure that the field would be populated.

5. Location I made the field size 50 because from looking at the data, I know that the ‘Location’ is only the continent in which the animal can be found. This means that the size does not need to be very large with this field. I also made sure that the record could not be duplicated and would be populated, using the same methods as with the previous fields.

6. Status The data items list told me that this field was coded, which meant that I needed to create a validation rule. I did this, as well as writing a validation text. I also used a ‘LookUp Wizard’ to make a drop-down menu. By unchecking the ‘Limit to List option, I ensured that my validation text would come up if an incorrect option was entered. I then made the field size 6 because the longest code, ‘Orange’ is 6 letters long, and any entry longer than that would be invalid. I used the same techniques to ensure that the field would be populated.

7. Threat This field was also coded and required a validation rule. I did the same for this field as I did for ‘Location’, creating a drop-down menu as well as both a validation rule and a validation text. I made the field size 1 as the code is only one character long. I ensured that the field would be populated. I tested the validation rule to ensure that it worked.

8. Weblink • This field meant that I had to change its data type to hyperlink. I made sure that the field would be populated.

9. Adoption Cost • I made the data type currency and set it to only accept 2 decimal places. I made sure that it would be populated.

10. Importing Data • I imported 173 records.

11. Data Entry Form I created a data entry form to make it easy to input new records into the database.

12. New Records • I went to the IUCN Red List website (http://www.iucnredlist.org/) to find information about three endangered species, which I input into my database using my data entry form. I decided to input birds because there were not very many birds in the database.

13. Feedback • Good user interactivity available through the buttons provided • Unassuming colour scheme which doesn’t detract from the information • Has included suitable drop down boxes and validation rules to prevent incorrect data entry