gr8whitewaldron
I learned to "cheat" for this. I create a list or combo box that references the same master table. In the row source, I use "SELECT DISTINCT" instead of the default DISTINCTROW. This way, only the unique values appear in the selection list.
Example: A loan tracking database where the type of loan is required to be entered. Instead of referencing another table to the loan_type, the query for the field references itself ... SELECT DISTINCT loan_type from loan.
Admittedly, for the first few records, it is a little awkward since the user will be creating new load types, but after more and more loan types are defined, fewer and fewer additional loan types are required. (And with custom lists or support table, some one still needs to enter the values.)
(This is just an example; a loan officer or bank manager would probably want more controls on loan types. But in your case, you have indicated that the user has fairly liberal access to adding new values.)
Yes, there is pretty cool coding out there for adding new values to list and combo boxes. Yes, it would be fairly easy to update another table (ie, tblLoanType). This is just a simple work around from a simple guy.
Richard