OnClick event not firing on combo

[GraeagleBill]

I have a popup form that contains a combo box bound to a simple query as RowSource. The KeyDown event fires okay where I look for vbKeyEscape, but no response when a row item is detected. Is there something "magic" about a combo on a popup? It works if I test it on a non-popup.

[Micron]

Your post title says onclick; your question suggests one of the update or change events isn't working?

when a row item is detected.

That means "selected"?

[GraeagleBill]

Neither After or Change fire when an item is "selected". I'm expecting the OnClick Event to fire when I select (Detect) and item in a combo dropdown.

[Micron]

Combobox OnClick doesn't work the way I suspect you're expecting it to, which is "I click on it and event should run". AFAIC, it's pretty useless as it only follows the AfterUpdate event and a few others that I suspect don't apply in your case. See https://docs.microsoft.com/en-us/off...ComboBox.Click

Note that this is a page from the entire Office vba. You'll find it very useful for questions like this and so many others.

[GraeagleBill]

Selects an item in a combo box or list box, either by pressing the arrow keys and then pressing the ENTER key or by clicking the mouse button.

Not sure I described the issue very well. The issue is when the combo box is dropped down, either by code or "clicking" on the down-arrow, and displaying the RowSource data line-by-line the OnClick event doesn't fire when I detect and item with the mouse. I'm expecting my Event Procedure to receive control so that code can take the appropriate path. The combo box works perfectly if I move it to a non-popup form so hence my mystery.

[Micron]

when I detect and item with the mouse

I don't know what that means either. If it means you're selecting an item (changing the current value or not) then clicking on that value and the click even isn't firing - it's not supposed to. For me, there is no difference if the form is popup or not. It behaves as described in the link I provided. Did you read it?
EDIT - I see that your quote comes from there. Will review.
So now I'm wondering if what you're saying is that if you drop down the list one way or another, then keyboard arrow down/up (or perhaps select a list item via code) and keyboard press enter key, the click event doesn't fire. If that's it, I'd do something else because the Enter key is a temperamental thing to deal with. While the form keypress property has to be set to true, I don't think it makes a difference in this issue. I suspect you'd need a keypress event and trap for Enter key. Or allow the user to do what should come naturally and select from the list manually instead of making things too 'automatic'. Or maybe use Tab key instead?

EDIT2 by any chance is the control or form in question unbound?

[GraeagleBill]

EDIT2 by any chance is the control or form in question unbound?

The popup form itself IS NOT bound, only the combo is bound.

[moke123]

The popup form itself IS NOT bound, only the combo is bound.

Bound to what? The combo has an underlying query but if it was bound, it would be bound to the form.
Whats supposed to happen when you make a selection? Maybe you should post your code.

[Micron]

The popup form itself IS NOT bound, only the combo is bound.

AFAIK that is not possible. I've never seen a list of fields from which one can be selected to bind a control to if the form isn't bound, and if you type one in yourself it should complain.

[GraeagleBill]

Sorry guys, got a bit hung up in what I guess is too much of a superficial understanding in using the word "bound". I usually think of bound as referring to an object's data dependency.

Anyway, below is a screenshot snippet of the form where one can observe the combo control hidden behind a row of three command buttons. And, below that screenshot is the code that, while I've done this sort of arrangement countless times, will not "fire" when the user selects/detects/clicks-upon one of the items displayed in the dropped-down list. Right or wrong, in my vocabulary the combo control is "bound" to the table that contains the names of archive files.

Private Sub cmdViewArch_Click()
Me.cboArchView.Visible = True    'Un-hide the combo control
Me.cboArchView.SetFocus          'Put the focus on the combo and
Me.cboArchView.Dropdown          'Show user library of archive files
End Sub

Private Sub cboArchView_Click()
Dim strArcFile As String

strArcFile = Me.cboArchView.Column(1)  'Capture whatever file name might have been selected

    If MsgBox(strArcFile & vbNewLine & _
             "archive file selected.  Do you want to simply" & vbNewLine & _
             "view the file or restore it as primary data?", vbYesNoCancel) = vbYes Then
               
               'BLAH BLAH BLAH
               
    End If

Me.cmdViewArch.SetFocus
Me.cboArchView.Visible = False

End Sub

Private Sub cboArchView_KeyPress(KeyAscii As Integer)
    If KeyAscii = vbKeyEscape Then
        Me.cmdViewArch.SetFocus
        Me.cboArchView.Visible = False
    End If
End Sub

[Micron]

I usually think of bound as referring to an object's data dependency.

I might have described it that way, which still makes me wonder. Put it this way: a form or report is bound to a table or query, either of which can be referred to as a domain. Thus if you said the forms domain was qryMyQuery, I'd still know what you're talking about.

Form/report controls are bound to fields, but in order for that to happen, the form/report itself must be bound. So in one of your statements you declared that the form was NOT bound but the combo is. The first part of this paragraphs says 'no way'. I'm open to being corrected if I'm the one who's not understanding.

The point I'm trying to arrive at is, if the combo is not bound (don't confuse that with having a row source property - we're talking about a control source property here in order to declare it as being bound) then the behaviour you're describing is normal. The OnClick event won't fire if the combo isn't bound. If you're not sure, you could post an image of the property sheet data tab for the combo so we can see the control source and row source properties.

[GraeagleBill]

First, I want to thank you for your extensive efforts to straighten out the "old geezer" on some important distinctions about binding. I did think that setting the RowSource of a control constituted binding.

So, where we are now is that the form is bound to the domain represented by the query QArchives. And, that the combo is bound to the field ArchFileName within that domain. Still, the OnClick DOES NOT fire when I click/detect/select a file name from among the list of files when the combo is down.

Below are the property sheets involved in our discussion:

[GraeagleBill]

Well gentlemen, we seem to have been dealing with a corrupted form. I should have been suspicious of that earlier, as I've seen it in the past where forms/report and/or controls are copied, which partially was done here. To solve this caper, I created the popup form in a blank DB, tested it successfully and then basically did the same thing in the app with a new form created "from scratch".

I did learn something about binding and binding terminology so not all was lost.

Thanks,
Bill

[Micron]

when I click/detect/select a file name from among the list of files when the combo is down

...and you are making this selection how? I don't see it in code, yet where else would it be if you're dropping the list down by code?

If I .Dropdown on a combo and select an item, the onClick event runs for me.

[GraeagleBill]

Works for me too after the form rebuild described in post #13