prototype

storyboard

<iframe src="https://docs.google.com/file/d/0B2ib_3viaHkWckdrR0R5ZVRRdU0/preview" width="640" height="480"></iframe>

house style

p1 corrections

p1

d2 evaluation

p7

query p5 and m4 macro and messages

form p4 unit 18

m2

p3 and m2 add on screenshots

p5 p6

Task 2 task 5

Data	Type
Username	Text
Password	Text
First name	Text
Last name	Text
Address	Text
Town	Text
County	Text
Postcode	Text
Accepted	Text
Film ID	Text
Genre	Text
Film Month	Text
Title	Text
Review ID	Text
Date Paid	Text
Amount Paid	Text
Comments	Text
Star Rating	Text
ID	Auto number
DOB	Date/time
Comments	Memo

d1

Accidental deletion of fields is a common error this can be prevented by putting a code on your database which prevents people from accessing this and allowing only certain people to view it. You may also make it so when on deleting the stuff in the database you need a code that people with the right to delete this are the only ones that have it so no data is falsely deleted.

This problem happens when an unmatched data type is used. Such as, if a database is used to keep record of the number of stock a business owns, it will go wrong but instead of putting a numerical value the clerk inputs a text value i.e. one instead of 1 etc. To stop this happening the database can be programmed to tell the user with an error code message, like the red stars like on online e-mail forms where you’ve used the wrong characters for a password.

A null value equals nothing there and is a blank space on a data sheet.  This is a problem as the database will not be able to work properly as it doesn’t understand the commands. It  will often have the true false or null option  if the database hasn’t been set to understand the option of a null. It won’t work, like registering for an account or something and missing out parts of information it needs on the form sheet.

Re-naming something or that wrong on a database can be a bad mistake, some cases worse though such as in the case of a bank as big as Barclay’s. This is usually a human error. If the glitch is spotted it won’t fix on its own so to avoid this sort of problem you’ll have to double check the information you’ve been given. This is why people who work in administration often repeat your information back to you, your name and how it’s spelt and so on.   

Validation in computers is similar to when real people verify it’s the process of checking the data. When a user inputs information into a database it’s more than often that they will type in something that doesn’t quite make sense of match. It would therefore be the job of the computer to make sure the information is correct and make sure that it’s correct. Then, it becomes the persons turn to verify that data. Social networks like Face book have checks which wards off possible users if they are under the age of 18.

M1

M1-


Referential integrity is a database concept. This type can garauntee relationships between tables these remain consistent. For this to work you need to have a primary and foriegn key.

A foreign key is a field in a relational table that matches a primary key column of another table. If cross referencing you can use the foreign key. Where as the primary key is unique for such as for some businesses such as stores ie : JD have card number for employees.. This is to identify them on their own and to be used to access past secuirity. As many other ways they can identify them for instance someone may try to access this. The use of a passcode to acess secuirity is a good way as someone may gain someone eleses card when they are not the owner of this.

p1