اموزش کامل Access 2010-En

[A M I R]

Access 2010

[h=3]Access Basics

Introduction to Databases


Introduction to Objects

Getting Started in Access

Managing Databases and Objects

---

[h=3]Working With Data

Working with Tables

Working with Forms

Sorting and ******ing Records

---

[h=3]Running Queries and Reports

Designing a Query

More Query Design Options

Creating Reports

Advanced Report Options

---

[h=3]Database Design Tips

Modifying Tables

Creating Forms

Formatting Forms

Designing Your Own Database
​

 

[A M I R]

[h=2]Introduction to Databases

[h=3]Introduction

Access 2010 is a database creation and management program. To understand Access, you must first understand databases.



In this lesson, you will learn about databases and how they are used. You will familiarize yourself with the differences

between data management in Access and Microsoft Excel. Finally, you will get a look ahead at the rest of the Access course.

​

 

[A M I R]

[h=2]Introduction to Databases

[h=3]What is a Database?

A database is a collection of data that is stored in a computer system. Databases allow their users to

enter, access, and analyze their data quickly and easily. They’re such a useful tool that you see them all the

time. Ever waited while a doctor’s receptionist entered your personal information into a computer, or watched

a store employee use a computer to see whether an item was in stock? Then you’ve seen a database in action.




The easiest way to understand a database is to think of it as a collection of lists. Think about one of the databases

we mentioned above-- the database of patient information at a doctor’s office. What lists are contained in a database

like that? Well, to start with, there’s a list of the customer names. Then, there’s a list of past appointments, a list with

medical history for each patient, a list of contact information... and so on, and so on.




This is true of all databases, from the simplest to the most complex. For instance, if you like to bake, you might decide

to keep a database containing the types of cookies you know how to make and the friends you give those cookies to. This

is one of the simplest databases imaginable. It contains two lists: a list of your friends, and a list of cookies.

However, if you were a professional baker, you would have many more lists to keep track of: a list of

customers, a list of products sold, a list of prices, a list of orders... it goes on and on. The more lists you add, the more complex the database will be.

In Access, lists are a little more complex than the ones you write on paper. Access stores its lists of data in

tables, which allow you to store even more detailed information. In the table below, the “People” list in the

amateur baker’s database has been expanded to include other relevant information about the baker’s friends.

If you are familiar with other programs in the Microsoft Office suite, this might remind you a lot

of Excel, which allows you to organize data in a similar way. And in fact, you could build a very similar table in Excel.





​

 

[A M I R]

[h=2]Introduction to Databases

[h=3]Why Use a Database?
If a database is essentially a collection of lists stored in tables, and you can build tables in Excel, why

do you need a real database in the first place? While Excel is great at storing and organizing numbers, Access

is far stronger at handling non-numerical data, like names and descriptions. Non-numerical data plays a big role

in almost any database, and it's important to be able to sort and analyze it.




However, the thing that really sets databases apart from any other way of storing data is connectivity. We call

a database like the ones you’ll work with in Access a relational database. A relational database is able to

understand how lists and the objects within them relate to one another. To explore this idea, let's go back to

the simple database with two lists: names of your friends, and the types of cookies you know how to make. You

decide to create a third list to keep track of the batches of cookies you make and who they’re for. Since you're

only making cookies you know the recipe for, and you're only going to give them to your friends, this new list

will get all its information from the lists you made earlier.

See how the third list uses words that appeared in the first two lists? A database is capable of

understanding that the "Dad" and "Oatmeal" cookies in the "Batches" list are the same things as

the "Dad" and "Oatmeal" in the first two lists. This relationship seems obvious, and a person would

understand it right away. However, an Excel workbook wouldn’t.




Excel would treat all of those things as distinct and unrelated pieces of information. In Excel, you'd have to

enter every single piece of information about a person or type of cookie all over again each time you

mentioned it, because that database wouldn't be relational like an Access database is. Simply put, relational

databases can recognize what a human can: that if the same words appear in multiple lists, they refer to the same thing.




The fact that relational databases can handle information this way allows you to enter, search, and analyze data

in more than one table at a time. All of these things would be very difficult to do in Excel, but in Access, even

complicated tasks can be simplified and made fairly user-friendly.





​

 

[A M I R]

[h=2]Introduction to Databases

[h=3]Taking the Access 2010 Tutorial [h=4]What to expect from this course

This course will not teach you how to build a database from scratch. It is designed for people who plan to use a pre-existing database, most likely in the workplace.


The course begins with a basic introduction to Access. You will become familiar with the structure of

an Access database and learn how to navigate around various windows and objects contained in it. As

the course goes on, you will learn how to enter information in a variety of ways. You will also learn

how to sort, retrieve, and analyze that information by running queries. After you understand how to

use your database, you’ll be introduced to tools that let you modify its structure and appearance.




By the end of this course, you will be able to use a database with confidence. You should also be able to alter it to best suit your needs.

​

 

[A M I R]

[h=2]Introduction to Databases

[h=4]Is this course right for you?
If you’ve read the description and think that this course fits your needs, then go ahead and jump in. As mentioned, this

course is primarily designed to teach people to use an existing database, but no matter what your eventual goal is, this

course can provide you a solid foundation to start with.




If you’re planning to create a system to keep track of personal information, carefully consider whether

or not you need the full functionality of Access in your database. While Access is an extremely useful

tool, setting up a new database can be difficult and time-consuming. If you don't necessarily need the

full connectivity of a relational database, consider managing your information with Excel, instead. If

you do decide to create your own database
​

 

[A M I R]

[h=2]Introduction to Objects

[h=3]Introduction

Databases in Access 2010 are composed of four objects: tables, queries, forms, and reports. Together, these objects allow

you to enter, store, analyze, and compile your data as you wish.


In this lesson, you will learn about each of the four objects and come to understand how they interact with each other to create a fully functional relational database.

​

 

[A M I R]

[h=2]Introduction to Objects

[h=3]The Access Objects
[h=3]Tables



By this point, you should already understand that a database is a collection of data organized

into many connected lists. In Access, all data is stored in tables, which puts tables at the heart of any database.




You might already know that tables are organized into vertical columns and horizontal rows.

In Access, rows and columns are referred to as Records and Fields. A field is more than just a

column: it’s a way of organizing information by the type of data it is. Every piece of information within

a field is of the same type. For example, every entry in a field called “First Name” would be a name, and every entry in field called “Street Address” would be an address.

Likewise, a record is more than just a row-- it’s a unit of information. Every cell in a

given row is part of that row’s record.

Notice how each record spans several fields. Even though the information in each record is organized

into fields, it belongs with the other information in that record. See the number at the left of each row? That’s

the ID number that identifies each record. The ID number for a record refers to every piece of information contained on that row.

Tables are good for storing closely related information. Say that you own a bakery and have a database that

includes a table with your customers' names and information like their phone numbers, home addresses, and

email addresses. Since these pieces of information are all details about your customers, you’d include them all

in the same table. Each customer would be represented by a unique record, and each type of information about

those customers would be stored in its own field. If you decided to add any more information-- say, the customer's

birthday-- you would simply create a new field within the same table.

​

 

[A M I R]

[h=2]Introduction to Objects

[h=3]Forms, Queries, and Reports
Although tables store all of your data, the other three objects offer you ways to work with

it. They are: forms, queries, and reports. Each of these objects interacts with the records stored in your database's tables.

​

 

[A M I R]

[h=2]Introduction to Objects

[h=4]Forms

Forms are used for entering, modifying, and viewing records. You have probably had to fill out forms

on many occasions, like when visiting a doctor's office, applying for a job, or registering for school. The

reason forms are used so often is that they're an easy way to guide people into entering data correctly. When

you enter information into a form in Access, that data goes exactly where the database designer wants it to go-- in one or more related tables.

Forms make entering data easier. Working with extensive tables can be confusing, and when you have connected

tables, you might need to work with more than one at once to enter a set of data. However, with forms, it's possible

to enter data into multiple tables at once, all in one place. Database designers can even set restrictions on individual

form components to ensure that all of the needed data is entered in the correct format. All in all, forms help keep

data consistent and well-organized, which is essential for an accurate and powerful database.





​

 

[A M I R]

[h=2]Introduction to Objects

[h=4]Queries
Queries are a way of searching for and compiling data from one or more tables. Running a query is like

asking a detailed question of your database. When you build a query in Access, you are defining specific

search conditions to find exactly the data you want.




Queries are far more powerful than the simple searches you might carry out within a table. While a search

would be able to help you find the name of one customer at your business, you could run a query to find the

name and phone number of every customer who's made a purchase within the past week. A well-designed

query can give information that you might not be able to find out just by looking through the data in your tables.

​

 

[A M I R]

[h=2]Introduction to Objects

[h=4]Reports

Reports offer you the ability to present your data in print. If you've ever received a computer printout of a

class schedule or a printed invoice of a purchase, you've seen a database report. Reports are useful, because

they allow you to present components of your database in an easy-to-read format. You can even customize a

report's appearance to make it visually appealing. Access offers you the ability to create a report from any table or query.

​

 

[A M I R]

[h=2]Introduction to Objects

[h=3]Putting it All Together
Even if you have a good idea of how each object can be used, it can initially be hard to understand

how they all work together. It helps to remember that they all work with the same data. Every piece

of data a query, form, or report uses is stored in one of your database tables.

Forms allow you to both add data to tables and view data that already exists. Reports present data from tables

and also from querieswhich, in turn, search for and analyze data within those same tables.




These relationships sound complicated, but in fact, they work together so well and naturally that we often

don't even notice when we're using connected database objects. Have you ever used an electronic card

catalog to search for a book at the library? Chances are, you entered your search in something that looks like this:

When you did that search, you were entering your search terms into a form that, in turn, created and ran a

query based on your request. When the query finished searching the database's tables for records that

matched your search, you were shown a report that drew information from the query and the related

tables-- in this case, a list of books matching your search terms. You could represent the connections between the objects like this:

Imagine if, instead of using these tools, you'd had to search within a giant table containing every book in the library

system. The relevant records would likely be spread out across many tables: a table for book titles and descriptions, a

table containing information about which books are checked in or out, and a table with each branch of the library, just to name a few.




You'd have to search at least three tables just to find a book, learn its location, and see whether it's checked in! It's easy to

imagine how difficult it could get to find the right book. If you weren't careful, you might even mess something up by

accidentally deleting or editing a record. It's easy to see how the database objects make this search much more manageable.




which is a database that is able to understand how different sets of data relate to one another. Situations like

the example above are exactly why people find relational databases so useful. Without a relational database, what

should be a simple task-- searching for a book and seeing if it's checked in and where-- becomes incredibly

complicated and time-consuming. Knowing how to use the four Access objects can make even complicated tasks fairly user-friendly.
​

 

[A M I R]

[h=2]Getting Started in Access

[h=3]Introduction

Whenever you're learning a new program, it's important to familiarize yourself with the program window and the tools within it. Working

with Access is no different. Knowing your way around the Access environment will make learning and using Access much easier.


In this lesson, you will familiarize yourself with the Access environment, including the Ribbon, the Backstage

view, the Navigation Pane, the Document Tabs bar, and the Record Navigation bar. You will also learn

how to navigate with a navigation form, if your database includes one.

​

 

[A M I R]

[h=2]Getting Started in Access

[h=3]Getting to Know Access 2010

If you are familiar with Access 2007, then you will notice that there are not too many

changes to the 2010 interface, other than the addition of the Backstage view.




However, if you are new to Access, you will first need to take some time

to familiarize yourself with the Access environment.

​

 

[A M I R]

[h=2]Getting Started in Access

[h=3]Working with Your Access Environment

The Ribbon and the Quick Access Toolbar are where you will find the commands you will use to do common

tasks in Access. If you are familiar with Access 2007, you will find that the main difference in the Access 2010 Ribbon

is that commands such as Open and Print are now housed in Backstage view.





​

 

[A M I R]

[h=2]Getting Started in Access

[h=3]The Ribbon

The Ribbon contains multiple tabs, each with several groups of commands. Some tabs, like Form

Layout Tools or Table Tools, may appear only when you are working with certain objects like forms

or tables. These tabs are called contextual tabs, and are highlighted in a contrasting color to distinguish them from normal tabs.

​

 

[A M I R]

[h=2]Getting Started in Access

[h=4]To Minimize and Maximize the Ribbon:

The Ribbon is designed to be easy to use and responsive to your current task, but

if you feel that it's taking up too much of your screen space, you can minimize it.




Click the arrow in the upper-right corner of the Ribbon to minimize it.

To maximize the Ribbon, click the arrow again.


When the Ribbon is minimized, you can make it reappear by clicking on a tab. However, the

Ribbon will disappear again when you are not using it.

​

 

[A M I R]

[h=2]Getting Started in Access

[h=3]The Quick Access Toolbar
The Quick Access Toolbar is located above the Ribbon, and it lets you access common commands no

matter which tab you are on. By default, it shows the Save, Undo, and Repeat commands. If you'd

like, you can customize it by adding additional commands.

Note that the Save command only saves the current open object. In addition, the Undo command will

not undo certain actions, like adding a record. Pay close attention to your information when using the

Undo command to make sure it has the desired effect.

​

 

[A M I R]

[h=2]Getting Started in Access

[h=3]Backstage View

Backstage view gives you various options for opening, saving, printing, and viewing more

information about your database. It is similar to the Office Button Menu from Access 2007

or the File Menu from earlier versions of Access. However, unlike those menus, it is a

full-page view, which makes it easier to work with.





​