Creating Forms for Data Entry
Build forms that make correct data entry fast and incorrect entry difficult.
By the end of this lesson you can
- Generate a form and modify it in Layout and Design view
- Arrange fields in the order staff actually work
- Add controls including combo boxes and validation
- Explain why data entry should go through forms rather than tables
Lesson Notes
Read through the key concepts before you try the challenge.
Forms exist to protect the data
Three staff share the supply database at Lakeside Medical Associates.
They enter records directly into the table. Every field of every record is visible and editable at once, and within a fortnight two rows have been overwritten by someone who tabbed into the wrong line. A form would have shown one record at a time, in a sensible order, with the calculated fields not editable at all.
Your task: Build a form that makes correct entry the path of least resistance.
A form shows one record at a time in a controlled layout. It can order fields to match the paper document someone is reading from, hide fields staff should not touch, label fields in plain language, and validate entries before they are committed.
| Control | Does | Use for |
|---|---|---|
| Text box | Displays and edits a field | Most fields |
| Combo box | Dropdown, optionally from another table | Category, provider — anything with a fixed set of values |
| List box | Shows several options at once | Short lists where seeing all options helps |
| Check box | A Yes/No field | Flags and toggles |
| Command button | Runs a macro or VBA | Save, find, open a related form |
| Subform | Shows related records from another table | A patient's appointments inside the patient form |
Building a usable supply entry form
Create a form three staff will use daily to add and update supply records.
- 1
Select the table, then Create > Form to generate a starting point.
The generated form is complete but laid out in table field order, which is rarely entry order. It is a scaffold to modify, not a finished product — and starting from it is far faster than building from blank.
- 2
In Layout view, reorder fields to match the delivery note staff read from.
Entry speed comes from not having to hunt. If the paper document lists item, quantity, then cost, the form should too — every mismatch between the document and the form is a place someone loses their position.
- 3
Replace the Category text box with a combo box bound to a Categories table.
This eliminates spelling variants entirely. Free-text categories are the most reliable way to make a database unsortable, because 'Medical' and 'medical' group separately in every report.
- 4
Set calculated and key fields to Locked, or remove them from the form.
Staff have no reason to edit ItemID or a computed total, and every editable field is a field that can be broken by a stray keystroke. Removing what is not needed is a design decision, not a limitation.
- 5
Set the tab order to follow the visual order.
Tab order does not update automatically when you rearrange fields. If it is wrong, tabbing jumps around the form unpredictably, which is both slow and a genuine cause of data landing in the wrong field.
Result: A form that is faster than the table and makes the common mistakes impossible.
Match the form to the document staff work from, constrain what can be typed, and fix the tab order after every rearrangement.
Why should staff enter data through a form rather than directly into the table?
Challenge
Apply what you've learned in this lesson.
Build a form someone else could use without training.
- Generate a form for your supplies table, then reorder the fields in Layout view to match a delivery note.
- Create a Categories table and replace the Category field with a combo box bound to it. Confirm free text is no longer possible.
- Lock or remove the ID and any calculated fields, then fix the tab order to follow the visual layout.
- Have someone else enter two records using only your form. Note every point where they hesitated, and fix one of them.
Finished this lesson?
Progress is saved in this browser only. It is not a grade — official progress lives in Brightspace.