First, if your dropdown list is dynamic (i.e. changeable) then you should base a form's dropdown on a secondary table that lists the options you want to display. Adding or editing or removing an option is a matter of adding, editing, or dropping a record in the table. And if you never show your users the navigation pane or any other internal DB structures, they won't be able to screw it up for you because they won't see this table of choices.
Second, as a stop-gap measure, there is a property for combo boxes where you listed the values it could display. Those values are enumerated in a string property that is not difficult to find. There are two related properties - .RowSourceType and .RowSource - that control what your list looks like.
IF you have a short static list, you can have a "Value List" for the row source type and if so, the actual list is in .RowSource as a complex string. If you have a value list, you alter the list by editing the .RowSource string. You should be aware that using this way to specify your list is limited in size, which is why you do better to make your combo boxes depend on tables or queries.
If on the other hand you have a query or table set aside, you put "Table/Query" as the row source type and then specify the actual query OR the name of the actual query.
Here is a link to explain it a little better, perhaps.
Office VBA reference topic
docs.microsoft.com