|
|
This is only a preview of the paper
Click here to register and get the full text.
Existing members click here to login
|
|
|
I started by first inputting my data into my tables in an Access database for which my Library database will be based upon. I first designed my Pupils table where I entered the field sizes that I said I would use in my design: I typed in all the data and I did this for three database tables that I have used including the book and rental table. I then went onto to set up my relationships between each table. I used a one to many, relationship for both tables. The first relationship that I have used was a one to many relationship between the student table and the rental table. The reason I used this was because a pupil is able to rent out more than one book (maximum of three) at any one time. Having a one-to-one relationship would mean that only one pupil could rent out only one book at any one time which would be completely impractical. The other one to many relationship I have used is one from the book table and a ‘many’ to the rental table. I used this because this means that one book can be rented out many times, however if I were top used a one-to-one relationship, The book would only ever been able to be rented out once. I then went on to design my queries. I first designed my pupil query, queering the first and second name of the pupil, of his form.
Approximate Word count = 965
Approximate Pages = 3.9
(250 words per page double spaced)
|
|
|
|
|
|