Automatically updating a combo box in Access 2010

I am working in Access 2010. I have a subform named Surgical with a combo box named procedureType. I have a list of procedures to be populated. I then want the combo box to automatically update with a procedure not in the list and the new procedure added to the list. I believe I will need a look up table to start with. Help setting up my look up table is easy and the next step is the VB programming for the combo box to automatically up data when a procedure not in the list is added by the user.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rey Obrero (Capricorn1)Commented:
see this link from Microsoft
Jeffrey CoachmanMIS LiasonCommented:
[No Points wanted]

Just an FYI, ...
Please make sure that the people "adding" these values are aware of the values already existing in the list.

It is very easy for an inexperienced user to "Add" a similar sounding value to a list.

For example, an existing value/procedure might be: "Tubal Ligation"
But a user might type in :
"Tubal Ligations"
"Tubebal Ligation"
"Tuble Ligation"

...And then "Add" these misspelled items to the list.

This will wreak havoc on your queries/filters for: "Tubal Ligation"


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I'm with Jeff on this one.  I have found very few applications over the years that actually needed to add values to combos on the fly.  Therefore, I almost never allow it, even with a popup form called by the not in list event.  I prefer to control access to the maintenance of these lists and restrict who can actually modify them.  Many years ago, I developed a mini-app to manage lookup lists and include it in all my applications.  It gives me a single place to store all simple lookups (complicated ones or ones with additional columns have their own tables and maintenance forms) and reports to print them.  I can mark the tables to allow "anyone", "authorized user", or "IT only" to add/change rows in the table.  Of course, referential integrity prevents anything bad from happening.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.