Microsoft Access Tutorial for Beginners: Step-by-Step

This walkthrough gets you from a blank screen to a working starter database. By the end, you will have created an Access file, built one table, entered (or imported) a few rows, opened a simple form, run a basic query, and previewed a report. Keep Access open and follow along — about 20 to 30 minutes if you stay with one small practice example. New to the product itself? Start with What Is Microsoft Access?, then return here to build.

Step 1: Opening Access and Creating a New Blank Database

Open Microsoft Access on a Windows PC. Access is a desktop app included with many Microsoft 365 plans; it is not available as a native Mac app.

On the startup screen, choose Blank Database (not a template). Templates are fine later; for learning, a blank file keeps every click intentional.

Give the file a clear name — something like `ContactsPractice` or `InventoryStarter`. Pick a folder you will remember (Documents or a project folder), then create the database. Access saves it as an `.accdb` file. That single file is your database for this tutorial.

You should land in a new database with a default table open or ready in the Navigation Pane on the left. If a starter table appears with a generic name, you will redesign it in the next step.

Tip: Note the full path where you saved the file. Beginners often "lose" their first database because they accepted a default folder without looking.

Step 2: Creating Your First Table and Setting Field Types

A table is where Access stores rows of data — one row per thing (a contact, a product, an order). Each column is a field with a data type that tells Access what kind of value belongs there.

Open Table Design from the Create tab (wording can vary slightly by Microsoft 365 build; look for Design View for a table). If Access already gave you Table1 in Datasheet view, switch that table to Design View instead.

Add a few fields. For a simple contacts practice table, try:

Primary key, simply: A primary key is the field (or fields) that uniquely identify each row. Think of it as a permanent ID badge. AutoNumber is the easiest beginner choice — Access assigns 1, 2, 3… and never reuses a value in that table. Set ContactID as the primary key if Access has not already.

Save the table and give it a real name, such as `Contacts`. Close Design View when you are done. Four to eight fields is enough for this tutorial — do not invent dozens on day one.

Step 3: Entering Data or Importing from Excel

Open your table in Datasheet view (the grid that looks a bit like Excel). Click into the first empty row under your fields and type a few practice records. Press Tab to move between fields. Access saves each row when you leave it — you do not need a separate "Save row" click for ordinary data entry.

Enter at least three rows so later steps have something to filter and report on.

Importing from Excel (optional)

If you already have a clean spreadsheet, you can import it instead of typing everything by hand.

1. Put column headers in row 1 of Excel and keep one logical list per sheet (contacts on one sheet, not mixed with notes and charts).
2. In Access, use the External Data options to import from Excel.
3. Point to your workbook, choose the sheet or named range, and confirm that the first row contains column headings.
4. Import into a new table for this tutorial so you can inspect the result without overwriting practice work.

After import, open the new table in Design View. Check that dates are Date/Time, money is Currency or Number, and IDs look right. Access sometimes guesses Short Text for everything — fix types before you build forms on top of bad guesses.

If your real goal is moving a messy multi-sheet business workbook into a proper database — not a quick practice import — use our move from Excel to a database guide. That path covers scoping, Access vs SQL, and when DIY import stops being enough.

Step 4: Building a Simple Form for Data Entry

A form is a screen for entering and editing one record at a time. Most people should work in forms, not raw table grids, once the database is in daily use.

Select your table in the Navigation Pane. On the Create tab, create a form based on that table (Form or Form Wizard — either is fine for a first pass). Access lays out your fields on a screen.

Open the form in Form view. Add a new record with the New blank record control (often a button or navigation control at the bottom of the form). Fill the fields and move to another record. Edit an existing row and confirm the table updates when you return to Datasheet view.

You do not need fancy buttons or VBA yet. A plain single-record form already teaches the habit that matters: users type into a controlled screen, and the table stores the data. If labels look cramped, switch briefly to Layout view or Design view, widen a control, and save.

Step 5: Creating a Basic Query (Filtering and Sorting)

A query asks a question of your table: "Show only contacts who signed up this year," or "Sort everyone by last name." It does not have to change the underlying data — Select queries simply return a filtered, sorted view.

On the Create tab, open Query Design. Add your Contacts table (or the table you imported). Close the table picker when the table appears in the design grid.

In the grid below, choose fields you want to see — for example LastName, FirstName, Email, SignupDate. Set Sort on LastName to Ascending. In the Criteria row under SignupDate, enter a simple test such as a date after a known practice value, or leave criteria blank the first time and only sort.

Run the query (Run on the Design ribbon, or the equivalent play control). You should see a datasheet of results — fewer columns, optional filter, sorted order.

Save the query with a clear name like `ContactsByLastName`. Reopen it anytime to refresh the same question against current data.

That is the core idea: tables store facts; queries ask questions. Later you will join related tables; today, one table is enough.

Step 6: Creating a Simple Report

A report is a printable or PDF-friendly layout of table or query results — directories, lists, summaries.

Select your table or the query you just saved. On the Create tab, create a report (Report or Report Wizard). Preview it. You should see your fields laid out for reading rather than editing.

Adjust lightly if needed: change the title, widen a column in Layout view, or remove a field you do not need on paper. Save the report as `ContactsList` or similar.

Print or export to PDF once so you see the end-to-end loop: data in a table → optional query → output people can share. That loop is what Access is for.

Common Beginner Mistakes to Avoid

No primary key. Without a unique ID, duplicates are hard to spot and relationships become guesswork. Use AutoNumber on day one unless you already have a trusted business ID.

One giant table for everything. Contacts, orders, products, and notes jammed into one sheet-shaped table recreates Excel's worst habits. Even a tiny app should plan separate tables that relate later. Start with how to design an Access database, then dig into keys and joins in the Access table relationship guide.

Not backing up the file. Your `.accdb` is just a file. Copy it to another folder or drive before big experiments, imports, or "I'll just delete these columns." If something goes wrong and the file will not open cleanly, see Access data recovery — and build a backup habit before you need recovery.

Skipping Compact & Repair forever. As the file grows, use Access's Compact and Repair occasionally on a copy first if you are unsure. It is routine maintenance, not a magic fix for bad design.

When to Stop DIY-ing and Get Help

This tutorial is for learning and small personal or single-user practice databases. Stop stretching DIY when:

• More than one person needs to edit at the same time on a shared network copy — locking, slowdowns, and corruption risk rise fast without a proper split design and network setup.
• The database feels slow with real data volumes, heavy forms, or awkward queries — that is usually design and indexing, not "Access being bad."
• You need it production-grade — real security expectations, reliable imports every morning, automated emails, audit-friendly processes, or a system leadership will depend on.

Those are normal growth signals. When the practice file needs to become a real multi-table business system, start with custom Access database design and development. Browse Access development services when you want a database built or repaired for daily business use, or contact us for a free consultation. We will tell you honestly whether a cleaned-up Access app, Access plus SQL Server, or another approach fits — without pushing you past what you need.

What You Should Have Now

You created a blank Access database, designed a table with sensible field types and a primary key, entered or imported data, used a form, ran a query, and previewed a report. That is the Access toolkit in miniature. Next: try a second related table (for example Orders with a ContactID), or rebuild the same example for inventory. When a practice file becomes something your team relies on, bring in structure and backups early — cheaper than fixing a DIY file after it turns critical.