Others

Manage Form Save Prompts and Add Table Fields in Microsoft Access

Huda QurayshiHuda Qurayshi Nov 22, 2026 868 views

Question details

The user wants to manage form design save prompts and add a field to an existing Access database.

Manage Form Save Prompts and Add Table Fields in Microsoft Access
Product
Microsoft Access 2016
Device & OS
not provided
Scenario
Users filter or sort a form, and the database designer wants to add a purchasing field to an existing table and related objects.
Observed behavior
Access may prompt users to save form design changes. The user also wants earlier records to remain intact when a new field is added.
Before you start

Open the form in Design View and check whether the prompt appears after changing a filter or sort order. Identify the table that stores the records and any queries, forms, and reports that need the new field.

Solution 1Recommended

Close the Access Form Without Saving Design Changes

Use a custom close button when filters or sorts cause unwanted prompts to save the form design.

Changing a filter or sort can change form properties and trigger a design save prompt. Choosing Yes can retain those property changes in the form design; it does not necessarily change the split-form layout.

The macro's Save setting controls design changes, not whether edited records are saved. Record edits remain subject to Access validation and normal record-saving behavior.

1
Disable the built-in close button

Open the form in Design View, select the form in the Property Sheet, and set Close Button to No on the Format tab.

2
Add a custom button

On the Design tab, use the Button control to place a close button on the form. Select the button and open its Property Sheet.

3
Create the close macro

On the button's Event tab, select On Click and create an embedded macro. Add CloseWindow, set Object Type to Form, enter the form's name, and set Save to No.

4
Test the form

Save the form design, open it in Form View, apply a filter or sort, and click the custom button. Reopen the form and check that it closes without saving the changed design properties.

Close the Access Form Without Saving Design Changes
Check other exit paths: Disabling the form's close button does not necessarily prevent users from closing the database or using other navigation controls. Test those paths separately, including how the form handles invalid or unsaved record edits.
Free Microsoft Office alternative

Work With Exported Access Data in WPS Office

WPS Office is a free, lightweight Office alternative with a familiar interface for working with compatible documents and spreadsheets. Export Access data to Excel to review it in WPS Spreadsheets; WPS Office does not replace Access forms, macros, or database management.

Review and edit spreadsheet data exported from AccessOpen and save compatible Microsoft Excel formats such as XLSXUse a familiar interface for a straightforward transition from Office spreadsheetsAccess free, lightweight tools for documents, spreadsheets, and presentations
microsoft office alternative - wps office

Frequently Asked Questions

Why does Access ask me to save a form after I filter it?

A filter or sort can change form properties that Access treats as design changes. A custom button using the CloseWindow macro action with Save set to No can close the form without saving those design changes.

Does Save No discard changes users made to records?

No. In the CloseWindow macro action, Save No refers to the form's design changes. Record edits follow Access's normal saving and validation rules.

What happens if someone clicks Yes on the form save prompt?

Access may save changed form properties, such as a filter or sort, as part of the form design. This does not necessarily alter the split-form layout.

Will a new table field be blank for older records?

Existing records generally show a blank or Null value in the new field unless a default or other database logic supplies a value. Check the field properties in table Design View.

Why doesn't my new field appear on a form or report?

The object's record source may not include it. Add the field to the underlying query in Design View, then use Add Existing Fields in the form or report to place it on the layout.