Adding an item to a combo box stopped working

Question

Adding an item to a combo box stopped working

Robert Walberg 5

I have a basic contact list table/form that includes a look up table for the Town field with 3 columns: TownID, Town, and PostalCode. I wrote code for the Town field in the After Event property that recognizes when a town is not in the table. The code prompts the user to enter the postal code for said new entry and adds this to the look up table (mostly small towns with a single postal code). All worked fine until it didn't. When I open an older version of the database, everything works as it should. But over time I made some changes to the form and with this new version all I get when new text is entered is a standard Access message (i.e., not of my making): "the text you entered isn't an item in the list". I've tried studying the older version but I didn't learn anything from that exercise. I put in a msgbox at the beginning of the code, and it doesn't appear. That tells me that after new text is entered, Access is going somewhere other than the After Event code. Can anyone help me out?

Robert Walberg 5 Reputation points

2026-01-07T06:53:52.37+00:00
Response to AI.

LimitToList is set to Yes.

I moved the code from the After event procedure to the NotInList event. Same bad outcome.

I'm not familiar with "breakpoints" so I inserted msgboxes:

Code works until the 3rd msgbox "Town doesn't exist". At this point, the standard Access message appears: "the text you entered isn't an item in the list".

Private Sub TownCombo_NotInList(NewData As String, Response As Integer) MsgBox "NotInList event triggered" 'Autofill postal code based on town Dim ID As Long Dim sPostalCode As String ID = Nz(DLookup("TownID", "TownT", "Town=""" & Town & """"), 0) If ID > 0 Then MsgBox "Town exists" 'Town exists, look up data PostalCode = DLookup("PostalCode", "TownT", "TownID=" & TownID) Else 'Town does Not exist, ask for it MsgBox "Town doesn't exist" sPostalCode = InputBox("Enter Postal Code", "Town Not Found") PostalCode = sPostalCode SQL = "INSERT INTO TownT ( PostalCode, Town ) " & _ "SELECT """ & sPostalCode & """, """ & Town & """" DoCmd.RunSQL SQL MsgBox "Postal Code Added to Town Lookup Table", vbInformation, "Donor Contact Form" End If

```vba
Robert Walberg 5 Reputation points

2026-01-07T08:10:22.72+00:00
Response to AI.

NotInList is set to Yes.

I moved the code from the After event procedure to the NotInList event. Same bad outcome.

I'm not familiar with "breakpoints", so I inserted msgboxes instead:

Private Sub TownCombo_NotInList(NewData As String, Response As Integer)

MsgBox "NotInList event triggered"

     'Autofill postal code based on /town

    Dim ID As Long

    Dim sPostalCode As String

     ID = Nz(DLookup("TownID", "TownT", "Town=""" & Town & """"), 0)

     If ID > 0 Then

MsgBox "Town exists"

    '/Town exists, look up data

        PostalCode = DLookup("PostalCode", "TownT", "TownID=" & TownID)

     Else

    'Town does Not exist, ask for it

MsgBox "Town doesn't exist"

        sPostalCode = InputBox("Enter Postal Code", " or Town Not Found")

        PostalCode = sPostalCode

        SQL = "INSERT INTO TownT ( PostalCode, Town ) " & _

            "SELECT """ & sPostalCode & """, """ & Town & """"

        DoCmd.RunSQL SQL

        MsgBox "Postal Code Added to Town Lookup Table", vbInformation, "Donor Contact Form"

    End If

End Sub

Code works until the 3rd msgbox "Town doens't exist". At this point, the standard Access message appears: "the text you entered isn't an item in the list".
Karl Donaubauer 3,191 Reputation points

2026-01-07T11:06:58.92+00:00
Hi,

The first code part which handles an already existing town should not be in the NotInList event but probably in the AfterUpdate event of the town control.

The code for the NotInList event should be sth like this:

Dim strSQL As String 'tell Access that you want to add a new entry Response = acDataErrAdded 'Newdata = the new value in the combo box' text part strSQL = "INSERT INTO TownT ( PostalCode, Town ) " & _ "SELECT """ & Newdata & """, """ & Me!Town & """" 'add record without confirmation message Currentdb.Execute strSQL, dbFailOnError

Servus
Karl

Access Forever News DevCon
Access-Entwickler-Konferenz AEK

5 answers

Your answer

Robert Walberg 5 Reputation points

2026-01-07T06:53:52.37+00:00

Response to AI.

LimitToList is set to Yes.

I moved the code from the After event procedure to the NotInList event. Same bad outcome.

I'm not familiar with "breakpoints" so I inserted msgboxes:

Code works until the 3rd msgbox "Town doesn't exist". At this point, the standard Access message appears: "the text you entered isn't an item in the list".

Private Sub TownCombo_NotInList(NewData As String, Response As Integer) MsgBox "NotInList event triggered" 'Autofill postal code based on town Dim ID As Long Dim sPostalCode As String ID = Nz(DLookup("TownID", "TownT", "Town=""" & Town & """"), 0) If ID > 0 Then MsgBox "Town exists" 'Town exists, look up data PostalCode = DLookup("PostalCode", "TownT", "TownID=" & TownID) Else 'Town does Not exist, ask for it MsgBox "Town doesn't exist" sPostalCode = InputBox("Enter Postal Code", "Town Not Found") PostalCode = sPostalCode SQL = "INSERT INTO TownT ( PostalCode, Town ) " & _ "SELECT """ & sPostalCode & """, """ & Town & """" DoCmd.RunSQL SQL MsgBox "Postal Code Added to Town Lookup Table", vbInformation, "Donor Contact Form" End If

```vba
Robert Walberg 5 Reputation points

2026-01-07T08:10:22.72+00:00

Response to AI.

NotInList is set to Yes.

I moved the code from the After event procedure to the NotInList event. Same bad outcome.

I'm not familiar with "breakpoints", so I inserted msgboxes instead:

Private Sub TownCombo_NotInList(NewData As String, Response As Integer)

MsgBox "NotInList event triggered"

'Autofill postal code based on /town

Dim ID As Long

Dim sPostalCode As String

ID = Nz(DLookup("TownID", "TownT", "Town=""" & Town & """"), 0)

If ID > 0 Then

MsgBox "Town exists"

'/Town exists, look up data

PostalCode = DLookup("PostalCode", "TownT", "TownID=" & TownID)

Else

'Town does Not exist, ask for it

MsgBox "Town doesn't exist"

sPostalCode = InputBox("Enter Postal Code", " or Town Not Found")

PostalCode = sPostalCode

SQL = "INSERT INTO TownT ( PostalCode, Town ) " & _

"SELECT """ & sPostalCode & """, """ & Town & """"

DoCmd.RunSQL SQL

MsgBox "Postal Code Added to Town Lookup Table", vbInformation, "Donor Contact Form"

End If

End Sub

Code works until the 3rd msgbox "Town doens't exist". At this point, the standard Access message appears: "the text you entered isn't an item in the list".
Karl Donaubauer 3,191 Reputation points

2026-01-07T11:06:58.92+00:00

Hi,

The first code part which handles an already existing town should not be in the NotInList event but probably in the AfterUpdate event of the town control.

The code for the NotInList event should be sth like this:

Dim strSQL As String 'tell Access that you want to add a new entry Response = acDataErrAdded 'Newdata = the new value in the combo box' text part strSQL = "INSERT INTO TownT ( PostalCode, Town ) " & _ "SELECT """ & Newdata & """, """ & Me!Town & """" 'add record without confirmation message Currentdb.Execute strSQL, dbFailOnError

Servus
Karl

Access Forever News DevCon
Access-Entwickler-Konferenz AEK

Answer 1

The problem with using the NotInList event procedure for inserting a new town or city into the relevant referenced tables is that town and city names can legitimately be duplicated, so if a list box includes a town name in its list, this might not be the same town as a new one of the same name which you want to insert. In the table the two would have different primary key values of course, but this will usually be in a hidden column in a combo box's RowSource, so you'll only see the name in the list.

One way to get round this is to use correlated combo boxes, so that the town or city combo box only lists those towns or cities in a region, e.g. a county , state or similar, selected in another combo box. You'll find an example of this in CorrelatedCombos.zip in my Dropbox public databases folder at:

https://www.dropbox.com/scl/fo/0scigd3r48hx5xrev2jrf/AB0-GMdTgMAO5O1cGdr3QW0?rlkey=ib6bs6g9jqcrywwzivur3265t&dl=0

In this little demo file a country, region, city, and postcode are selected in four correlated combo boxes, of which the first two are unbound, as to have columns in the the referencing Contacts table for these would introduce redundancy into the table. The demo also illustrates how to use the NotInList event procedure in this context, so that, as well as inserting the town or city name into the referenced Cities table, the correct RegionID value is also inserted.

Answer 2

Gabriel-N 16,565 Microsoft External Staff Moderator

Dear Robert Walberg

Thank you for posting your question in the Microsoft Q&A forum.

I took a look at the combo box behavior you mentioned where Access still shows “The text you entered isn’t an item in the list” even after you add the Town. One thing that often causes this is the NotInList event not setting the Response value in a way that tells Access the new value has been handled. Could you try adding the lines in your code?

' After your DoCmd.RunSQL statement:
MsgBox "Postal Code Added to CityTown Lookup Table", vbInformation
Response = acDataErrAdded  ' This suppresses the Access error and refreshes the list

Also, it would be worth double-checking the combo box setup. If the combo is bound to TownID (numeric) but NewData is the Town name (text), Access may still fail the re-check after the insert and show the built-in message again.

If possible, could you share a small sanitized sample .accdb via private message so I can reproduce the issue and investigate more thoroughly?

User's image

Hope this helps. If you can share the sample, I’ll take a closer look and get back to you with specific recommendations.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Robert Walberg 5 Reputation points

2026-01-07T09:06:09.0366667+00:00
Thanks Gabriel.

I added your code and it didn't make a difference.

I believe the combobox is bound to CityTownID. Control Source = CityTownID and Bound Column property is "1", which is CityTownID. If I change it to 2, then the field converts from text to numerical (i.e., CityTownID number).

The database is split. There is a back end file of the tables. Does that affect sending you a sample file? How do I "sanitize" a sample? I tried deleting sensitive data in the tables with a copy and entering sample data, but the CityTown field on the form wouldn't react to the CityTown lookup table. It would put in the town name, but not the postal code, which is a whole new problem.

My question is why does an older version work and not the newer version when I did not change the CityTown event code, but made changes in other areas of the form code? The changes I made were primarily to prevent the user from leaving the form before filling in required fields. My guess is that this is the area that caused the problem.

To clarify, the actual names are "CityTown". I tried to simplify it to just "Town" for the posting.
Gabriel-N 16,565 Reputation points Microsoft External Staff Moderator

2026-01-07T11:03:44.6733333+00:00

Dear Robert Walberg

Thanks for the detailed update.

You mentioned you recently added validation to prevent users from leaving the form before filling in required fields. That’s very likely the culprit. As a quick test, could you temporarily disable the newly added validation code (by “commenting it out”) and then try the CityTown combo box again? If the combo starts working normally, we’ll know the new validation is interfering with the combo box event flow.

Regarding the sample: could you please send me both the front-end and back-end files via the private message I sent you? That way I can reproduce the issue exactly. The private message thread isn’t public; only you, me, and the moderators can see it; so your data stays confidential.
Gabriel-N 16,565 Reputation points Microsoft External Staff Moderator

2026-01-08T09:57:49.5333333+00:00

Dear Robert Walberg

Hope you are doing well. Please try the methods suggested by Ken and Karl to see if they help resolve the issue. If the problem persists, feel free to share the files via private message so I can take a closer look.

Answer 3

Robert Walberg 5

I spoke too soon. The new design and code worked as I wanted. Unfortunately, even within a very simple database, other problems arose. Not being well-versed on Access and especially VBA coding (learning on the go), I could not fix them in a timely manner (worst time of year-busy season) So, I worked on reverting to my earlier version. In other words, I'm back to square 1. For now, I manually add new data into the lookup table. Fortunately, the bulk of the data is already in the table. There are few new entries. When I have more time, I'll give it another go.

Another downside that I encountered with the text box approach is that I have to type the whole city or town. With a combo box typing 1-3 letters gets you the city/town you want.

One positive that came out of ths is that I now populate 3 field based on 1 field when recording a new contact, which is 1 more than before. Save some time and is more accurate.

Gabriel-N 16,565 Reputation points Microsoft External Staff Moderator

2026-01-19T15:31:37.9+00:00

Hi Robert Walberg , sorry you had to revert your updates. Whenever you’re ready to revisit the combo box issue, feel free to reach out, I’m happy to help you get it working.
Robert Walberg 5 Reputation points

2026-01-20T04:28:53.4133333+00:00

I did revisit the combo box issue last night and am happy to report I have had some success. I have more persistence than skill or knowledge of Access and coding. Part of the problem seemed to point to another combo box (ProvinceID), one that I created in the earlier versions. I went back to the basic DonorT table and added a short text field (Province). I populated the short text field using the Update Query and the numerical field (ProvinceID) before deleting the numerical field relationship. Then on the DonorF form, I replaced the combo box with a text box and set the Control Source property to the new short text field. Finally, I successfully wrote the VBA code in the AfterUpdate Event for the CityTown combo box to search the CityTownT lookup table to autofill province and postal code based on the town. BTW, if you are wondering why I chose city/town instead of postal code, there are 3 reasons: (1) most of my data is based on towns with a single postal code. (2) It is quicker and easier to start typing a city/town name to locate the city/town, usually 2-3 letters. Our postal codes are 1A1 A1A format-more difficult to type. (3) There are not many new cities/towns to add. It is limited by geography. Our charity is local and services a finite region.

The change in the relationships did cause some other problems that I did not anticipate (lack of knowledge & experience working with Access). Before last night, I didn't have time to work out the glitches. It was easier to go back to the former design. Armed with a little bit of knowing what the problem was and my persistence, I did fix the glitches. Everything works again.

My next step is to code the CityTown combo box field to prompt the user for data when a city/town is not in the list. I am able to open the CityTownT lookup table to add new data, but eventually someone else will be using the database. Assuming they are not versed in Access design, I don't want them fiddling with the tables. I have split the database, so the table designs are safe and data can be added. It would be easier if the next user didn't have to go into the tables. Eventually, I hope to remove the navigation pane so that opening objects is not an option. Until then, I need the navigation pane to continue my design.

I will let you know how I do and will definitely ask you for help, if needed.
Robert Walberg 5 Reputation points

2026-01-20T07:15:50.2266667+00:00
Okay, I do need help. Below is the code I started (I didn’t include the autofill code, just the DLookup code). My plan is to use the value of ID in an If-Then statement (i.e., If ID>0 use current data, Else prompt user for new data and insert into lookup table).

Private Sub CityTownCombo_AfterUpdate()

MsgBox CityTownCombo

Dim ID As Integer

ID = Nz(DLookup("CityTownID", "CityTownT", "CityTownID=""" & CityTownID & """"),0)

MsgBox ID

MsgBox CityTownCombo returns a numerical value equal to the current city/town (e.g., “1”)

MsgBox ID returns “Run-time error ‘3646: Data type mismatch in criteria expression”

In the code, the last CityTownID = 1, the correct numerical value for the current city/town in the combo box.

In the code, ID = 0. I expect it to equal 1, the CityTownCombo value

I tried Dim ID as Long, but got the same bad result

Here’s what I’m working with:

DonorT (table) has a CityTownID field (data type: Number)

CityTownT (lookup table) has a CityTownID field (data type: AutoNumber) and 3 fields: “CityTown”, “Province”, and “PostalCode” (all data type: Short Text)

Combo box is named “CityTownCombo”. Control source = “CityTownID (from DonorT table)

Combo box includes all 4 fields from the CityTownT lookup table (CityTownID AutoNumber field not visible)

Combo box value is stored in the CityTownID field in the DonorT table.

Row Source: SELECT [CityTownT].[CityTownID], [CityTownT].[CityTown], [CityTownT].[Province], [CityTownT].[PostalCode] FROM CityTownT ORDER BY [CityTown];

I can’t figure out where the mismatch in data type is! BTW, the msgboxes are there for verification. They won’t be in the final code.
Gabriel-N 16,565 Reputation points Microsoft External Staff Moderator

2026-01-20T14:43:35.5833333+00:00

Hi Robert Walberg

Thanks a lot for the feedback and the extra details, I really appreciate it.

Could you give me a little time to rebuild a small test version on my side and run through some troubleshooting?

Once I’ve done that, I’ll get back to you with what I find, and hopefully we can get this resolved.

Gabriel-N 16,565 Microsoft External Staff Moderator

Hi Robert Walberg

I was able to reproduce your issue using the settings described below.

User's image

The Run‑time error 3464 (Data type mismatch) in your AfterUpdate event is likely caused by the syntax in your DLookup criterion. You may try updating it to the following: ID = Nz(DLookup("CityTownID", "CityTownT", "CityTownID=" & Me.CityTownCombo), 0) to determine whether the error is resolved.

However, because Limit To List = Yes is already enabled and you have a functioning NotInList event, the AfterUpdate event might not unnecessary. When a user enters a new town, the NotInList event captures the entry, inserts it, and Response = acDataErrAdded instructs Access to refresh the control automatically. Access will handle the ID update internally without requiring any additional code in AfterUpdate. Below is the VBA code I used in my test environment:

Private Sub CityTownCombo_NotInList(NewData As String, Response As Integer)
    Dim sPostalCode As String
    Dim strSQL As String
    ' Ask the user if they want to add the new item
    If MsgBox("City/Town '" & NewData & "' is not in the list. Do you want to add it?", _
              vbQuestion + vbYesNo, "Add New?") = vbYes Then
        ' Prompt for Postal Code
        sPostalCode = InputBox("Enter Postal Code for: " & NewData, "New Entry Details")
        ' If the user entered a code (did not leave it empty)
        If Len(sPostalCode) > 0 Then
            ' Create SQL Insert statement
            ' Note: I set Province to an empty string '' to keep it simple.
            ' You can add another InputBox for Province if you want to be thorough.
            strSQL = "INSERT INTO CityTownT (CityTown, PostalCode, Province) " & _
                     "VALUES ('" & Replace(NewData, "'", "''") & "', '" & _
                     Replace(sPostalCode, "'", "''") & "', '')"
            ' Execute command to add to DB
            CurrentDb.Execute strSQL, dbFailOnError
            ' Tell Access: The data is added, please requery the list
            Response = acDataErrAdded
        Else
            ' User cancelled Postal Code entry
            Response = acDataErrContinue
            Me.CityTownCombo.Undo
        End If
    Else
        ' User selected No at the start
        Response = acDataErrContinue
        Me.CityTownCombo.Undo
    End If
End Sub

Since I do not have access to your exact form configuration, this solution may not fully align with your environment. Please try the above suggestions, and if the issue persists, feel free to send me a screenshot of your ComboBox, tables, relationship settings or VBA code via private message. Only you, myself, and the moderation team will be able to view it.

Gabriel-N 16,565 Reputation points Microsoft External Staff Moderator

2026-01-26T06:59:18.7433333+00:00

Hi Robert Walberg

Is there any update from you?

If yes, please feel free to let me know.
Robert Walberg 5 Reputation points

2026-01-27T02:34:55.3966667+00:00

Gabriel

It's one of my busier times using the database. I can't afford to mess it up. I should have more time later this week. I will be in touch.
Gabriel-N 16,565 Reputation points Microsoft External Staff Moderator

2026-01-27T11:47:25.8633333+00:00

Hi Robert Walberg

Thanks for letting me know. Please take your time and get back to me whenever you're free. I appreciate the update and will wait to hear from you.
Robert Walberg 5 Reputation points

2026-02-02T08:09:03.2466667+00:00

Gabriel

Changing the DLookup syntax in the AfterUpdate Event didn't make a difference. But as you stated, it isn't necessary.

Good news/bad news. Good news is that your code works in the NotInList Event, but I'm sure you knew that. However, I do want to add "Province". I created a string variable ("sProvince") and added an input box. As a check, I added "MsgBox strSQL" to the code, and when I run a sample it returns

Naturally, the Province column of the lookup table is empty. That tells me that I have to replace the empty string (Value 3) with sProvince, but with all the single and double quotes and ampersands, I can't get it right. I have no programming experience except for this database. I tried to learn the SQL INSERT function as well as the proper use of single and double quotes and concatenation. I'm pretty good at concatenating names and addresses. The INSERT function is straightforward enough until single and double quotes are called for. I can't grasp that part of it. I gather from your code that I need to insert a "Replace(sProvince, ...)" statement somewhere, but I can't get it right. When I don't know what I'm doing, I revert to trial and error. Is my analysis correct? Please help!
Duane Hookom 26,820 Reputation points Volunteer Moderator

2026-02-02T12:23:13.4166667+00:00

Does your Province field allow zero length strings? You could allow them or attempt to insert Null rather than ''.
Gabriel-N 16,565 Reputation points Microsoft External Staff Moderator

2026-02-02T17:03:15.9066667+00:00

Hi Robert Walberg

Apologies for the delayed response. I truly appreciate your patience, please allow me a bit more time to review this thoroughly, and I’ll follow up with you by tomorrow.

Gabriel-N 16,565 Microsoft External Staff Moderator

Hi Robert Walberg

Please try using this VBA code as it worked successfully in my testing environment. The input panels will appear just like the ones shown in the image.

In this code, I changed the last part of the SQL string from ... & "', '')" to: ... & "', '" & Replace(sProvince, "'", "''") & "')"

This inserts your sProvince variable safely.

User's image

Private Sub CityTownCombo_NotInList(NewData As String, Response As Integer)
    Dim sPostalCode As String
    Dim sProvince As String     ' <--- New Variable
    Dim strSQL As String
    
    If MsgBox("City/Town '" & NewData & "' is not in the list. Do you want to add it?", _
              vbQuestion + vbYesNo, "Add New?") = vbYes Then
        
        ' 1. Prompt for Postal Code
        sPostalCode = InputBox("Enter Postal Code for: " & NewData, "New Entry Details")
        
        ' 2. Prompt for Province (Only if Postal Code was entered)
        If Len(sPostalCode) > 0 Then
            sProvince = InputBox("Enter Province for: " & NewData, "New Entry Details")
            
            ' 3. Build the SQL String
            ' I have broken this down into multiple lines to make it easier to read.
            ' The pattern is: VALUES ('Town', 'Zip', 'Province')
            
            strSQL = "INSERT INTO CityTownT (CityTown, PostalCode, Province) VALUES ('" & _
                     Replace(NewData, "'", "''") & "', '" & _
                     Replace(sPostalCode, "'", "''") & "', '" & _
                     Replace(sProvince, "'", "''") & "')"
            
            ' DEBUG: Remove this line after testing
            ' MsgBox strSQL 
            
            CurrentDb.Execute strSQL, dbFailOnError
            Response = acDataErrAdded
        Else
            Response = acDataErrContinue
            Me.CityTownCombo.Undo
        End If
    Else
        Response = acDataErrContinue
        Me.CityTownCombo.Undo
    End If
End Sub

I hope this approach works well for you.

Robert Walberg 5 Reputation points

2026-02-04T03:29:33.15+00:00

That's got it. Thanks Gabriel. My error was in the "Replace..." line for "Province": & "')". I didn't have the correct single and double quotes. Plus, I had to reactivate part of the AfterUpdate to autofill "Province". Should be smooth sailing from here. I can't thank you enough.
Gabriel-N 16,565 Reputation points Microsoft External Staff Moderator

2026-02-04T15:11:24.14+00:00

Hi Robert Walberg , I'm really glad to hear your issue has been resolved! If anything else comes up or you're unsure about something, feel free to post your question in the forum. It's not just me, the whole community is here and always happy to support you.

Answer 4

Problem solved, I hope. I noticed that the older version that worked used a text box and not a combo box. After fiddling with the combo box approach, I decided to try the text box method.

In the newer version, I added a field to the DonorT table with Data Type = Short Text (the combo box was linked to a number field). I switched out the combo box field with the text box field. The VBA code is all in the AfterEvent procedure, and it much the same as the older version.

I also added a Province field to the CityTownT, so this table contains the City/Town, Province, and Postal Code field. When I enter a city or town and the data is already in the table, the 3 field are automatically populated. If the city or town is not found, the user is prompted for the information. Ultimately, the new data is entered into the look up table. I can post the code if anyone is interested.

My question is, is this OK or am I setting myself up for future problems?

Answer 5

It sounds like your issue with the combo box may stem from how the NotInList event is being triggered or handled in your updated form. Here are a few steps you can take to troubleshoot the problem:

Check the LimitToList Property: Ensure that the LimitToList property of the combo box is set to Yes. This setting is crucial for the NotInList event to be triggered when a user enters a value that is not in the list.
Review the Event Procedure: Make sure that the event procedure for the NotInList event is correctly set up. The procedure should handle the addition of new entries to the lookup table. If the procedure is missing or not correctly linked to the event, it won't execute.
Debugging: Since you mentioned that the message box does not appear, it indicates that the code may not be executing at all. You can try placing breakpoints in your code to see if it hits the NotInList event when you enter a new town. This can help you determine if the event is firing as expected.
Check for Changes in the Form: Since you mentioned making changes to the form, review those changes to see if anything might have inadvertently affected the combo box's behavior. For example, ensure that the combo box is still bound to the correct data source.
Requery the Combo Box: After adding a new town to the lookup table, ensure you are using the Requery method to refresh the combo box list so that it includes the newly added value.

If these steps do not resolve the issue, you may want to compare the properties of the working older version of the database with the new version to identify any discrepancies.

References:

Share via

Adding an item to a combo box stopped working

5 answers

Your answer