Others

Add New Combo Box List Values in Microsoft Access

Kushani NimanthikaKushani Nimanthika Nov 22, 2026 868 views

Question details

Add values to an Access combo box list as users enter data, including in a database shared by multiple employees.

Add New Combo Box List Values in Microsoft Access
Product
Microsoft Access
Device & OS
not provided
Scenario
Employees need to enter records and add new choices to a shared combo box list.
Observed behavior
A combo box used directly in a table does not expose the NotInList event needed to add a new value through an event procedure.
Before you start

Identify the table and text field that store the list values, and check that users have permission to add records to that table. The example below assumes a single-column text list; an ID-based lookup requires a different setup.

Solution 1Recommended

Use a bound form and the combo box NotInList event

Use this approach to let users add a new text value while entering a record through a form.

This example assumes a source table named ListValues with a text field named ValueName, and a form record field that stores the same text. Adapt the table and field names to your database.

1
Create a bound form

Select the table or query containing the records, then choose Create > Form Wizard and create a form for data entry.

2
Configure the combo box

Open the form in Design View and add a combo box. In its Property Sheet, set Control Source to the record field, Row Source Type to Table/Query, and Row Source to SELECT [ValueName] FROM [ListValues] ORDER BY [ValueName];. Set Limit To List to Yes.

3
Open the event procedure

In the combo box Property Sheet, select the Event tab. Set On Not In List to [Event Procedure], then click the ellipsis button to open the VBA editor.

4
Insert the new value

In the generated NotInList procedure, enter the following code, keeping the procedure name Access created: Dim qdf As DAO.QueryDef On Error GoTo AddError Set qdf = CurrentDb.CreateQueryDef("", "PARAMETERS [pNew] Text (255); INSERT INTO [ListValues] ([ValueName]) VALUES ([pNew]);") qdf.Parameters("pNew").Value = NewData qdf.Execute dbFailOnError Response = acDataErrAdded Exit Sub AddError: MsgBox "The value could not be added: " & Err.Description Response = acDataErrContinue

5
Test a new entry

Save the form, open it in Form View, and type a value that is not in the combo box list. Confirm that the value is added and can be selected in a record.

Use a bound form and the combo box NotInList event
Prevent duplicate list values: Consider setting the ValueName field's Indexed property to Yes (No Duplicates) in table Design View. If another user adds the same value first, the example displays an error; select the existing value after refreshing the list.
Free Microsoft Office alternative

Work with Office files in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format compatibility for easier migration. It does not replace Access forms or run Access NotInList events.

Use a familiar interface for documents, spreadsheets, and presentations.Open and edit compatible DOCX, XLSX, and PPTX files.Manage simple lists in spreadsheets alongside your Access workflow.
QA img-9

Frequently Asked Questions

Can I use NotInList directly in an Access table?

No. Use a combo box on a form, then configure its On Not In List event in the control's Property Sheet.

Why isn't the NotInList event firing?

In the combo box Property Sheet, check that Limit To List is set to Yes and On Not In List is set to [Event Procedure]. Test by typing a value that is not already in the list.

What does acDataErrAdded do?

Setting Response to acDataErrAdded tells Access that the event procedure added the value. Access then requeries the combo box list so it can use the new entry.

Does the text-list example work for an ID-based lookup?

Not without changes. If the combo box stores a numeric ID while displaying text, the procedure must add the text to the lookup table and handle the new ID and the combo box's bound column.

Where should employees open a split database?

Each employee should open a local front-end copy. Its linked tables should point to the back-end file in a shared network location, which can be checked through External Data > Linked Table Manager.