Assessment task 2 part 1 Activity 3
1.0 Database information
1.01 Definition of database 3
1.02 The history of database 3
1.03 Database introduction 3
(1) Database consist 3
(2)Design a database 3
(3)Basic design rules 4
(4)Relationships between tables 4
(5) How to set up relationship 5
2.0 The funeral benefits of using database through
2.01 Funeral benefits of using database 5
2.02 Operate of database 5
This report is a word-processed report to explain what databases are and how they work. This report contains illustrations from the database provided. It has some cases for using database software. In this report I will talk about illustration and explanations of relationship between tables using.
1.0 Database information
A simple definition of a database is a structured collection of related data about one or more subjects.
In normal daily life we make frequent use of databases, such as looking for a telephone directory or using an address book.
1.02 The history of database
With the advent of broadband communications, businesses and consumers alike demand real-time access to databases over the Net. Make sure you’re ahead of the curve by updating your programming skills to the latest database technology.
1.03 Working with a database
When working with a database you require more than just the data. In order to manipulate, process and present your data as information you require a set of utilities.
Forms are used to input, edit or view information in your databases records by record. You can see what you want in the way that you want to see it. Forms can be created to imitate your paper documents. A query is a question you ask Access about your data: how many accounts are overdue and what customers do we have in Kirkcaldy? Whenever you ask Access a query you get the latest up to date information contained in the databases. Reports are used to print and view information from your databases. Reports allow you to produce your information in the way that you want and enable you to: group information and perform calculation such as totals and averages. 1.04 How to work and the relationship between tables in the
database and the benefit to set up such structure.
(1) Database is consisting of: table, field and record.
Table is a collection of records related by subject, for example a customer list. Field is the individual data items used in a table, for example – Name,
Business, Address, Telephone Number Contact Name. The record is the information about a single item, for example – Jim Andrew,
(2) Design a database: What do you want?
You must first establish why you require your database and what you expect to get from it. It is most important to define your output needs first.
What have you got?
Knowing what you want then allows you to look critically at what data you have and make decisions as to how it should be structured in terms of fields and tables.
What do you to do?
This question asks you to look at any manipulations you need to carry out in order to achieve your information output: searches, sorts, and calculation.
Define your needs.
In order to clarity your needs it is often useful to draw a simple diagram and/or write a short narrative. If the database is being designed for others, show them your sketch/narrative and use it to check your understanding of their requirements.
(3) Basic design rules: Make each record unique.
Each table should be allocated a primary key. A primary key is simply a field or a combination of fields that makes a record unique. Give your table primary key to ensure you have no duplicate records. Select the primary key yourself or let Access select it for you. If you let Access define the primary key, it will add a counter field at the beginning of each record. Although this guarantees the uniqueness of the record. Although this guarantees the uniqueness of the recode, it does mean that two records could contain identical data (apart from the key itself).
Make fields functionally dependent.
Each field in the record should relate to the subject of the record. If it doesn’t, it’s either redundant or it belongs in another table!
Ensure fields don’t contain calculated or
As an example, you need only hold gross pay and deductions on a person’s salary record. Net pay can be calculated when it is required, when printing a report showing the pay slip for instance.
Ensure each field is independent. You should be able to alter any one field in a record without affecting any of the others.
Ensure data is in its smallest logical parts.
It is useful, for instance, to keep customers’ postcodes separate from the
rest of their addresses so that you can analyse sales based on postal regions.
The difficult part of building a new database is the design stage. Creating it is a fairly simple business.
(4) Relationships between tables
Relationships Databases are those where the data is held in a number of cross-referenced tables in order to reduce duplication. They make it easier to find, analyse, maintain and protect your data because it is all held in one place.
The type of relationship is one-to-one and one-to-many
In the one-to-many examole
show to the left, the field linking
the two tables is Supplier ID. In
The Products table, this is
shown by the fact that it is
(5) How to set up relationship:
Open the database called a name, click on the relationship button on the toolbar and the relationships dialog box will open. Within that, the show table dialog box will open. If not, go on the view menu and select show table. Click on the name of the table which you want to take, then click on add. Repeat for the orders table and then click on close.
2.0 The funeral benefits of using database through USAPITAS 2.mdb.
2.01 Funeral benefits of using database: increased speed, easy to use,
store very large amounts of data, allow for easy inputting and editing of data, automatic updating and recalculating of data, allow for easy storing of data, allow for easy seating and selection of data, format, arrange and present information in the way that you want it, share the information with other software applications/programs and on networks, electronic database allow you to share one set of information amongst many users and therefore reduce duplication.
2.02 Database using through USAPITAS 2.mdb.
USAPITAS 2.mdb has provided many tables for us, through theses tables we could do some jobs as they ask.
If we want to do something about the database, first we should open Microsoft Access. Choose to create a New Blank Database. Ensure that you save this database in an appropriate place, such as your floppy disk. When prompted for a name of the database, call it a name. Click on create. We could create table in design view, by using wizard and by entering data. In the objects we can see them: tables, queries, forms, reports, pages, macros and modules, through them, we could do useful things in our work. Now, let us set an example from USAPITAS 2.mdb. It has many
tables, which have already built for us; we could do jobs from them like that. In the job, it asks to build queries and reports.
firstly we need to see clear the table and the demand, then click query or report in the object, then we could build them through in design view or by entering data, we usually use design view, because it could set up many conditions, which is suit the job.
The design view like the left
picture, the first one on the
The right picture is design view
interface. When you fill all
content in the design view then
you can keep it, at last you have
The specific benefits for USAPITAS about the database is very important, through the database, the company could manage the staff information easier, and it also could change the information together, or it can help people to check the information more quickly.
This report is talking about all parts of database, explaining the objectives or purpose here. And an explanation of what databases are and how they work. It is also to illustrate the structure of this database, explain the relationships between tables, benefits of setting up such structures and the general benefits of using databases. This report uses the USAPITAS 2.mdb to be the example to explain it carefully.
6.<<Software Applications Packages >>