combo box pulldown "blinks" with roquery on got focus

[markjkubicki]

behind the GotFocus event of a combo box, i have code for a a requery; however doing so creates this odd effect (which does not happen when the line of code is commented out)
when the user first clicks the combo, the drop-down list opens, the immediately closes.
on a second click, it behaves normally: the drop-down opens and waits for a user action.

involved are (3) tables:
tbeFixtureTypeDetails


tbeSubIssueSchedule
tbeSubIssueSchedule_Types

the user creates a record in tbeSubIssueSchedule
then adds to it records in the related table tbeSubIssueSchedule_Types
entries for tbeSubIssueSchedule_Types are pulled from tbeFixtureTypeDetails

the parent form is a single record form (data source: tbeSubIssueSchedule)
on it is a continuous record SUBform (data source subform tbeSubIssueSchedule_Types)
the COMBOBOX is on this sub form and is used to add records to the table tbeSubIssueSchedule_Types from tbeFixtureTypeDetails

the intent is for the pulldown to show all records in tbeFixtureTypeDetails that are NOT already being used for the current tbeSubIssueSchedule.

behind the combobox i have the ridiculous query (although, it does work, albeit with this strange glitch)

SELECT tbeFixtureTypeDetails.Type, qrySubSchedule_currentTypesUsed.type
FROM tbeFixtureTypeDetails LEFT JOIN qrySubSchedule_currentTypesUsed ON tbeFixtureTypeDetails.Type = qrySubSchedule_currentTypesUsed.Type
WHERE (((qrySubSchedule_currentTypesUsed.type) Is Null))
ORDER BY TDASort_AlphaCnt([tbeFixtureTypeDetails]![type]), tbeFixtureTypeDetails.Type;

it includes references to the query qrySubSchedule_currentTypesUsed which is

SELECT tbeSubIssueSchedule_Types.SubIssueTitle, tbeSubIssueSchedule_Types.type
FROM tbeSubIssueSchedule_Types
WHERE (((tbeSubIssueSchedule_Types.SubIssueTitle)=[forms].[frmSubIssueSchedules_Entry].[txtSubIssueTitle]));

I think I've made this FAR more complicated than it ought to be, and I'll appreciate in advance any thoughts, suggestion, direction...

be well, stay healthy,
m.

[Bob Fitz]

Can you show us the code in the Got Focus event

[markjkubicki]

Private Sub cboType_GotFocus()
    Me.cboType.Requery
End Sub

[Gicu]

Can you see if you still get the flicker if you use the Enter event instead?
https://docs.microsoft.com/en-us/off...0Enter%20event.
Cheers,

[Micron]

You can give a combo the focus by clicking on the button as well as the data portion so it's an odd one in that respect. I can imagine your problem by dropping down the list, thereby giving it the focus, causing it to requery which causes it to drop back up. On a subsequent click, it already has the focus so the requery doesn't run. If you must requery when interacting with that control, try the Enter event instead. Usually one requeries a combo based on some other action, such as choosing a value from a different combo (as in cascading combos). Maybe in your case, you could also use form's Current event, but that would cause a requery of the combo each time a new record is selected and once upon form opening.

[markjkubicki]

TOTALLY INTERESTING: this odd/unique: '... focus by clicking on the button as well.. '

...moving the requery to the Enter event, nor the Current was effective; BUT !!! moving it to the EXIT event did.

thnx so much

[Micron]

I can't imagine how requerying the combo after it loses focus does anything of value, but if you're happy then I guess we are too.