I'm using Access 2010 with a form containing a list box.
The code I'm using for the KeyPress event in the list box, calls the
after update event for the same control. But somehow, it is also
triggering a call to the Click Event.
It's happening on one form, but not on another with a similar set up.
Can anyone point me in the right direction?
--
Bob Darlington
Brisbane

"Bob Darlington" <bob (AT) dpcman (DOT) com.au> wrote

The up & down arrow keys trigger a click event in listboxes. Could these be
the keys you're trying to control? If so, consider using the KeyDown event
to detect them, then destroy the keypress using KeyCode = 0. I'm pretty sure
that'll occur before they are passed to the listbox.

Select Case KeyCode
Case vbKeyDown
KeyCode = 0
'process the key here
Case KeyUP
KeyCode = 0

....

On 30/12/2011 9:36 PM, Stuart McCall wrote:
THe KeyPress event reads the KeyCode (Character) and tries to match a
record starting with that character in the ListBox. It finds the first
record OK every time (for any character), and sets a module level
variable to record its index and calls the ListBox AfterUpdate event
(which applies the form filter etc).
But when the same key is pressed again (looking for a second instance
with the same first character) the ListBox flashes to the correct
record, and then reverts to the previous record.

Further testing using message boxes shows that:
1. The KeyPress event occurs once
2. The AfterUpdate event occurs 3 times (called once each by the
KeyPress and Click events and once from somewhere I can't detect).
3. The Click event occurs once.

The KeyDown event is used disabled at present.
If I break the code and step through after the KeyPress message box
(right at the beginning of the event sub), the AfterUpdate event only
gets called once, the Click event doesn't get called and all works as
intended.

I'm obviously missing something to do with ListBox behaviour, but what?



--
Bob Darlington
Brisbane