Week 9 unit 3

This week I have successfully created two more calculated fields within my student database in order to work out how much each pupil owes (to work out how much remains to be paid for 2b select information) as well as creating a relationship between the two tables; student database and the parent database.

Creating calculated fields:

 To work out how much each pupil owed, I had to begin by adding a calculated field that stated the discount (if any) added to the students if they had attended both revision sessions. This was so that I could see their reduced amount to pay which helped find out whether they had paid all of this. To work this out, I had entered this expression shown on the screenshot on design view for this field;

It is saying if it is true that they've attended both revision classes, a discount should be given. 

For the next calculated field, it would immediately determine the amount each pupil owed. The field name was 'Amount owed'. This expression was as follows; 

This is asking the field to deduct the discount as well as the amount paid from the overall prom cost. This is how i created my calculated fields, simply by adding these expressions. My full method will be available under 2e develop information as per usual. 

this is the two calculated fields (discount and amount owed).

Relationships 

I have also created relationships so data redundancy doesn't occur. This fits in with the overall aim of the project. Create a solution that the organiser can use. This relationship has made the organisation much better as it has reduced the likelihood of errors. Below screenshots linked to this part of the system can be found;