4.1 Records: Adding and Editing Data

ICDL Using Databases Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About the ICDL Using Databases Module How the Module Is Tested & How to Use This Guide

2 Understanding Databases

2.1 What a Database Is: Data vs Information 2.2 How Databases Are Organised: Tables, Records, Fields 2.3 Data Types, Field Properties, Primary Keys & Indexes 2.4 Relationships & Referential Integrity (Concepts)

3 Using the Application

3.1 Working with Databases 3.2 Common Object Tasks: Objects, Views, Navigation, Sorting

4 Tables

4.1 Records: Adding and Editing Data 4.2 Table Design: Fields, Data Types, Properties, Validation, Keys, Indexes 4.3 Table Relationships: One-to-Many & Referential Integrity

5 Retrieving Information

Search & Filters Building Queries: Single/Two-Table, Criteria & Comparison Operators Advanced Query Criteria: Logical Operators, Wildcards, Editing & Running

6 Forms

6.1 Creating and Using Forms

7 Outputs: Reports, Export & Printing

Reports: Creating, Grouping & Summaries Exporting Data: Spreadsheet, Text, CSV, XML & PDF Printing Tables, Forms, Queries & Reports

4.1 Records: Adding and Editing Data

Key Takeaways Explain This Topic AI

A record is one complete row in a table representing a single entity, such as one customer or one product

A field is one column in a table representing a single data element, such as a surname or a price

You can add a new record using the blank row marked with an asterisk (*) at the bottom of Datasheet view

Deleting a record removes the entire row and cannot be undone once the database saves the change

Access saves changes to a record automatically when you move to another record, so there is usually no explicit save step

Last updated: July 2026

Every database task ultimately comes down to working with data inside tables, and the ICDL Using Databases exam tests this at the most granular level: can you add a record, edit a value, and delete a record without hesitation? This section covers Task Items 3.1.1 and 3.1.2 from the official syllabus — the foundation skills you will use constantly while working in Datasheet view.

Records vs Fields: The Core Distinction

Before touching any data, you need to be completely fluent in two terms that the exam uses interchangeably with their everyday equivalents:

A record is a row. Each record holds all the information about one specific person, product, order, or other entity. If a table stores customers, one record is one customer.

A field is a column. Each field holds one single piece of information that is common to every record — a surname, a phone number, a price. A field never mixes multiple kinds of data.

• Term Table equivalent Contains Example
• Table Whole grid All records of one subject type tblCustomers
• Record One row All field values for one entity Customer "J. Naidoo"
• Field One column One data element, repeated per record Surname

A simple way to remember this for the exam: if you can point to a single cell where a row and a column intersect, that cell holds one field value belonging to one record . Confusing "record" and "field" is one of the most common wrong-answer traps on this exam, because they sound similar but describe perpendicular concepts — records run horizontally, fields run vertically.

Adding a New Record

In Datasheet view (the default spreadsheet-like grid view for a table), Access always keeps one blank row available at the bottom, marked with an asterisk (*) in the row selector on the left. To add a record:

Open the table in Datasheet view.

Click into the row marked with the asterisk, or click New (blank) record on the navigation bar at the bottom of the window.

Type values into each field, pressing Tab or Enter to move to the next field.

Move to another row (or close the table) — Access saves the record automatically.

A new blank row always appears below the record you just finished, so you can keep adding records without any extra menu steps. If a field has a primary key with AutoNumber as its data type, that field fills in automatically and cannot be typed into — this is covered in more depth in the next section on table design.

Modifying Data Within a Record

Editing an existing value is just as direct: click into the field you want to change, and either retype the whole value or use the keyboard to edit part of it (Home, End, Backspace, and Delete all behave as expected inside a field). Access marks the row you are currently editing with a pencil icon in the row selector — this is a visual cue that the record has unsaved changes still in progress. As soon as you move off that row, the pencil icon disappears and the change is committed.

Some practical points the exam expects you to know:

You do not need a Save command for individual records. Moving to a different record, or closing the table, commits the edit. This is different from documents in a word processor, where you must save explicitly.

Undo (Ctrl+Z) only works while the pencil icon is showing. Once you move off the row and the edit is committed, Undo may no longer be able to reverse a field-level change.

Editing a field value never changes which record it belongs to — you are always working within one record at a time, even though a table displays many records together.

Deleting a Record

To delete a record: click the row selector at the left edge of the record to highlight the whole row, then press Delete (or use the ribbon's Delete Record command). Access displays a confirmation warning because record deletion is permanent — there is no built-in "undo delete" for records once confirmed.

Important distinctions for the exam:

Deleting a record removes the entire row — every field value that belonged to it disappears.

Deleting the data inside a single field (e.g., clearing just the phone number) does not delete the record — the record still exists with an empty value in that one field.

If a record is linked to related records in another table through a relationship with referential integrity enforced, Access will block the deletion (or warn about cascading deletes) rather than silently orphaning the related data. Relationships and referential integrity are covered fully later in this chapter.

Multiple Records at Once

You can select several adjacent records by clicking the first row selector and shift-clicking the last one, then deleting them together in a single confirmation. This is faster than deleting rows one at a time, but the same permanence warning applies — always confirm you have selected the correct range before deleting.

Putting It Together

Adding, editing, and deleting records is the daily-use skill set behind every other database task on this exam: you cannot build a meaningful query, form, or report until the underlying table actually holds accurate data. Keep the record/field distinction sharp, remember that Access auto-saves individual record edits, and always treat record deletion as a one-way action.