You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
آموزش کامل Access 2007-EN
- شروع کننده موضوع A M I R
- تاریخ شروع
[h=2]Exploring an Access Database
[h=3]Parts of a Database
A Microsoft Access database is made up of several components including tables, forms, queries, and reports. These
components are called database objects. One or more of these objects are formed when a database is created, and
all the objects appear in the Navigation Pane. To make the database easier to navigate, beginning Access users may
want to reorder the objects in the Navigation Pane.
[h=3]Parts of a Database
A Microsoft Access database is made up of several components including tables, forms, queries, and reports. These
components are called database objects. One or more of these objects are formed when a database is created, and
all the objects appear in the Navigation Pane. To make the database easier to navigate, beginning Access users may
want to reorder the objects in the Navigation Pane.
[h=2]Exploring an Access Database
[h=5]To Change how Objects are Ordered in the Navigation Pane:
If you are new to databases, arranging the objects by type in the Navigation Pane is usually a
good idea. This will group tables, forms, queries, and reports in individual groups in the pane.
[h=5]To Change how Objects are Ordered in the Navigation Pane:
- Click the drop-down arrow at the top of the Navigation Pane to see the ordering options.
- Select a menu option. The Navigation Pane will appear reordered based on your selection.
If you are new to databases, arranging the objects by type in the Navigation Pane is usually a
good idea. This will group tables, forms, queries, and reports in individual groups in the pane.
[h=2]Exploring an Access Database
[h=3]Parts of a Database (cont.)
A database is made up of several components, or objects. These objects include:
We'll look at each of these objects in more detail in later lessons, but you can access them from the Navigation Pane like you can with tables.
[h=3]Parts of a Database (cont.)
A database is made up of several components, or objects. These objects include:
- tables
- queries
- forms
- reports
We'll look at each of these objects in more detail in later lessons, but you can access them from the Navigation Pane like you can with tables.
[h=2]Exploring an Access Database
[h=5]Tables
A table is the database object that contains the basic information you wish to store. A
blue and white icon represents the table in the Navigation Pane.
In the Customer Info table below, there are columns, or fields, of information including title and author. Each
row is a record that contains the information specific to the fields listed.
[h=5]Tables
A table is the database object that contains the basic information you wish to store. A
blue and white icon represents the table in the Navigation Pane.
In the Customer Info table below, there are columns, or fields, of information including title and author. Each
row is a record that contains the information specific to the fields listed.
[h=2]Exploring an Access Database
[h=5]Queries
Another database object is called a query. A query allows you to retrieve information from one
or more tables based on a set of search conditions you define using the table fields.
For example, if you want to know the name of the books that have sold in Colorado and Kansas, you
could create a query that would retrieve information from multiple tables to determine the answer. In
this example, you would retrieve information from the Order table and Books table. Queries are covered in more detail in later lessons.
[h=5]Queries
Another database object is called a query. A query allows you to retrieve information from one
or more tables based on a set of search conditions you define using the table fields.
For example, if you want to know the name of the books that have sold in Colorado and Kansas, you
could create a query that would retrieve information from multiple tables to determine the answer. In
this example, you would retrieve information from the Order table and Books table. Queries are covered in more detail in later lessons.
[h=2]Exploring an Access Database
[h=5]Forms
A third database object is the form. Forms are an Access tool that users can create to make data entry in database tables easier.
Entering data directly into a table can be difficult if there is a lot of information to enter. Like an Excel
spreadsheet, an Access table is essentially a screen filled with blank rows where a user
enters records. Forms, however, provide users with an easy-to-read interface where they can
enter table data. Forms are especially useful for Access users that aren’t comfortable working with databases.
[h=5]Forms
A third database object is the form. Forms are an Access tool that users can create to make data entry in database tables easier.
Entering data directly into a table can be difficult if there is a lot of information to enter. Like an Excel
spreadsheet, an Access table is essentially a screen filled with blank rows where a user
enters records. Forms, however, provide users with an easy-to-read interface where they can
enter table data. Forms are especially useful for Access users that aren’t comfortable working with databases.
[h=2]Thinking about Database Design
[h=3]Introduction
The first step in creating a database is to think about why you need it -- what is its purpose? Once you
know that, you can begin designing your own database. Ask yourself questions like: What kinds of information
will it store? How will I have to break that information down, so it can be stored in my database? How will I
use the data once it's in there?
This lesson will walk you through the steps of database design, using a bookstore scenario. You will
determine the purpose of the database, and plan the tables and fields you will need for a very simple bookstore database
[h=3]Introduction
The first step in creating a database is to think about why you need it -- what is its purpose? Once you
know that, you can begin designing your own database. Ask yourself questions like: What kinds of information
will it store? How will I have to break that information down, so it can be stored in my database? How will I
use the data once it's in there?
This lesson will walk you through the steps of database design, using a bookstore scenario. You will
determine the purpose of the database, and plan the tables and fields you will need for a very simple bookstore database
[h=2]Thinking about Database Design
[h=3]Designing a Database
[h=5]The Ready-2-Read Bookstore Scenario
The best way to learn about designing a database is to jump right into the process. Let's pretend
we work for the Ready-2-Read bookstore and we need to build a database for the store to use. Let's
think about what we might need the database to do for us.
The following diagram shows that we have customers, and we sell books via orders, both in the store and online.
The store needs a way to keep track of these things.
[h=3]Designing a Database
[h=5]The Ready-2-Read Bookstore Scenario
The best way to learn about designing a database is to jump right into the process. Let's pretend
we work for the Ready-2-Read bookstore and we need to build a database for the store to use. Let's
think about what we might need the database to do for us.
The following diagram shows that we have customers, and we sell books via orders, both in the store and online.
The store needs a way to keep track of these things.
[h=2]Thinking about Database Design
[h=5]Determine the Purpose of the Database
The first step of designing a database is to determine the purpose of the database. What do we need it to do?
At Ready-2-Read, our customers will place orders for books. At the very least, we will want our
database to track the books we sell, the customers we sell them to, and the date of each of the orders.
The database will also be able to tell us where our customers live when we need to send them books or
coupons. Additionally, we can use it to track our sales or to make a bestseller list to post in the store.
[h=5]Determine the Purpose of the Database
The first step of designing a database is to determine the purpose of the database. What do we need it to do?
At Ready-2-Read, our customers will place orders for books. At the very least, we will want our
database to track the books we sell, the customers we sell them to, and the date of each of the orders.
The database will also be able to tell us where our customers live when we need to send them books or
coupons. Additionally, we can use it to track our sales or to make a bestseller list to post in the store.
[h=2]Thinking about Database Design
[h=5]Plan Database Tables
Once you have established the purpose, you can begin brainstorming about how to break the information
up into the tables that your database will need to store the data. Recall that a table is a collection of
records and each record is broken up into the smallest pieces of needed information, called fields.
Since we are planning a database to track our customers, the books we have, and the orders our
customers place, we will need a table for each one of these.
TIP: Keep your database usable to others by giving your tables simple, easy to understand names.
[h=5]Plan Database Tables
Once you have established the purpose, you can begin brainstorming about how to break the information
up into the tables that your database will need to store the data. Recall that a table is a collection of
records and each record is broken up into the smallest pieces of needed information, called fields.
Since we are planning a database to track our customers, the books we have, and the orders our
customers place, we will need a table for each one of these.
TIP: Keep your database usable to others by giving your tables simple, easy to understand names.
[h=2]Thinking about Database Design
[h=5]Plan Table Fields
Once you know what tables you need, the next step is deciding what fields belong in each table. Remember
that fields are the smallest chunk of information in any record.
Let's look at our Ready-2-Read bookstore example again. There will be several fields in our Customers
table. We'll obviously want their first name and last name. We'll also need an address if we need
to send the customer his order. Email will be necessary if we need to contact the customer when
there is an issue with their order.
We will also need several fields in the Books table. Title and Author make sense for books. We'll need a
Price for each book. Category will help us know what type of books sell the best, so we can order more
books that fit into that category.
The Orders table will have fewer fields. We'll need this table to track the Customer who is placing the
order, the Book the customer is ordering, and the Date the order is placed.
Don't worry if your plan doesn't include every possible field you may need. Access lets you add fields to tables any time you think you need another one!
[h=5]Plan Table Fields
Once you know what tables you need, the next step is deciding what fields belong in each table. Remember
that fields are the smallest chunk of information in any record.
Let's look at our Ready-2-Read bookstore example again. There will be several fields in our Customers
table. We'll obviously want their first name and last name. We'll also need an address if we need
to send the customer his order. Email will be necessary if we need to contact the customer when
there is an issue with their order.
We will also need several fields in the Books table. Title and Author make sense for books. We'll need a
Price for each book. Category will help us know what type of books sell the best, so we can order more
books that fit into that category.
The Orders table will have fewer fields. We'll need this table to track the Customer who is placing the
order, the Book the customer is ordering, and the Date the order is placed.
Don't worry if your plan doesn't include every possible field you may need. Access lets you add fields to tables any time you think you need another one!
[h=2]Setting up Tables and Fields
[h=3]Introduction
Now that we have a handle on what the database should look like, we need to work on setting up our tables and the fields within those tables.
This lesson will walk you through the steps of setting up a database in Access 2007. You will be setting up tables
according to the plan for our bookstore scenario. You will also be setting up the fields for each table, including
establishing what data types can be entered in a given field.
[h=3]Introduction
Now that we have a handle on what the database should look like, we need to work on setting up our tables and the fields within those tables.
This lesson will walk you through the steps of setting up a database in Access 2007. You will be setting up tables
according to the plan for our bookstore scenario. You will also be setting up the fields for each table, including
establishing what data types can be entered in a given field.
[h=2]Setting up Tables and Fields
[h=3]
[h=3]
[h=3]Setting Up Tables and Fields
[h=3]Creating a New Database with Access
When you launch Access 2007, you will see the Getting Started window.
In the left pane, the template categories including the featured local templates are listed, as well as the
categories on Office Online. Templates are pre-built databases focused on a specific task that you
can download and use immediately.
You will also see the New Blank Database option that allows you to build your own database from scratch.
When you choose the New Blank Database option at the top of this window, you will be prompted to rename
the database from the default name, which is Database1.accdb. Rename the database whatever you would
like the name to be. In the example below, we named the database Ready2Read since that is the name
of the store in our scenario.
Click Create to finish naming the database.
[h=3]Creating a New Database with Access
When you launch Access 2007, you will see the Getting Started window.
In the left pane, the template categories including the featured local templates are listed, as well as the
categories on Office Online. Templates are pre-built databases focused on a specific task that you
can download and use immediately.
You will also see the New Blank Database option that allows you to build your own database from scratch.
When you choose the New Blank Database option at the top of this window, you will be prompted to rename
the database from the default name, which is Database1.accdb. Rename the database whatever you would
like the name to be. In the example below, we named the database Ready2Read since that is the name
of the store in our scenario.
Click Create to finish naming the database.
[h=2]Setting up Tables and Fields
[h=3]Setting up Tables
The new database opens with one table showing as a default. It also defaults to naming this table Table1 in
both the Navigation Pane, and the Table tab itself. You will want to name your tables based on your database design plan.
[h=3]Setting up Tables
The new database opens with one table showing as a default. It also defaults to naming this table Table1 in
both the Navigation Pane, and the Table tab itself. You will want to name your tables based on your database design plan.