Okay, I've determined what the problem is.
I actually have an unbound subform. The subform retrieves records from
TableA. But is doesn't select all records, it selects DISTINCT records. So
if there are 20 records in the table, then currently only two are returned
and shown in the subform.
So, I guess when I try to select an item from the combobox (for either of the
two records shown), then Access isn't sure what to do, because of the
Distinct.
I've verified this by removing the Distinct in the SQL statement and having
the full 20 records shown. The combobox works fine and an item can be
selected from the drop down list and displayed in the text box portion of the
combobox.
I've got a similar posting to this with regards to deleting these distinct
rows from the subform. There I'm having the same problem.
I guess I need to try and intercept these user actions or maybe create a
query to run the subform against (the Query would only contain the Distinct
two records) which would allow for combobox selection and deletion. But I
still need to update TableA if something changes in the Query. Again, I'm
not sure where I would intercept Access automatic processing in order to
cause these changes to occur.
robert said:
Thanks, Steve.
This seems to work, but I'm currently unable to select an item from the
dropdown list. I keep getting a "beep" and the selected item is not entered
into the "text" portion of the combobox. I've placed a break in the Enter
event, to see if this is being executed when I select an item from the
dropdown list. But it doesn't seem to be.
The combobox is not locked and is enabled.
Any ideas?
Thanks.
[quoted text clipped - 4 lines]