H
hpi
Hi,
I already posted this earlier to comp.databases.ms-access but I guess
this group is more suitable.
I have 2 listboxes (and some other stuff) on a form
The first listbox has an onclick event which, when fired, adds an item to
the second list box and sets the selected item to the last item which makes
sure the lists scrolls when full.
When I click an entry in the first list, the item is added and selected
which is ok.
After this, each click on any control on the form, causes the click event
from the first list to be fired.
I found out that first setting focus to the second list box solves the
problem but I don't understand why this is necessary.
Is this normal behaviour?
tx
HPI
PS: I'm doing this using access 2003 on XP
I already posted this earlier to comp.databases.ms-access but I guess
this group is more suitable.
I have 2 listboxes (and some other stuff) on a form
The first listbox has an onclick event which, when fired, adds an item to
the second list box and sets the selected item to the last item which makes
sure the lists scrolls when full.
When I click an entry in the first list, the item is added and selected
which is ok.
After this, each click on any control on the form, causes the click event
from the first list to be fired.
I found out that first setting focus to the second list box solves the
problem but I don't understand why this is necessary.
Is this normal behaviour?
tx
HPI
PS: I'm doing this using access 2003 on XP