T
Tim K
I already solved my problem after a day of struggle, but thought I'd post
the lesson learned. (Turns out to be my stupidity, but someone might learn
from it.)
It's that old problem where if I entered a new value in the combo box, I
could get the new value added to the lookup table, but the combo box list
would not refresh with the new value. Tried Response = acDataErrAdded,
combobox.Requery, yadda yadda.
But then I noticed even when I closed and reopened the form, the combo box
did not list the dozen new entries that were now in the lookup table. That
led me to discover the real problem--the combo box row source was based on
the same query as the control source. And that query has an inner join to
the lookup table, meaning that any new values, which didn't get joined to
records in the main table, don't get picked up.
Giving the row source its own query to just the lookup table did it. Duh.
the lesson learned. (Turns out to be my stupidity, but someone might learn
from it.)
It's that old problem where if I entered a new value in the combo box, I
could get the new value added to the lookup table, but the combo box list
would not refresh with the new value. Tried Response = acDataErrAdded,
combobox.Requery, yadda yadda.
But then I noticed even when I closed and reopened the form, the combo box
did not list the dozen new entries that were now in the lookup table. That
led me to discover the real problem--the combo box row source was based on
the same query as the control source. And that query has an inner join to
the lookup table, meaning that any new values, which didn't get joined to
records in the main table, don't get picked up.
Giving the row source its own query to just the lookup table did it. Duh.