>>I have found something:
>>
>>1) added a new property to my combobox : aWrongcontrol
>>2) populate the array with all the controls which will be coverred by the dropdown combobox
>>3) in the downclick:
>>parse the array aWrongcontrol and make all properties involved invisible
>>4) in the click event
>>Do While Inkey("HM") ! 0
>>dodefault
>>enddo
>>parse the array aWrongcontrol and make all the properties involved visible
>>
>>Regards,
>>
>>Koen
>
>I think this sounds a lot like a kludge and suggests to me that a form re-design would probably be a cleaner solution.

And is sure to look ugly and confuse the user even better if the FCQ (frequently clicked control :) is only partially covered with the dropdown, but made wholesale invisible while it's dropped down.

A perhaps less horrible kludge would be to place an invisible shape under the dropdown, which is the old and venerable dirty trick we all used when painted in the corner. It just eats the extra click and vanishes as soon as the combo loses focus. Not sure whether the z-order of this control would screw things up if it was added in .combo.gotfocus(), but perhaps if it was added after all other controls but before the combo - i.e. the combo would have to be on top of it in z-order (better to set this shape on top, then combo on top so they are above everything else but combo is still above the shape).

I understand that the previous paragraph is jumble/jungle, but I'm counting on you guys to properly guess what I had in mind :).