>Naomi, I consider few who criticizes a thing after having seen it,
>because who doesn't have the ability to foresee the result
>it cannot have the ability to judge it.
>It can clearly have the power to do it, but this is another thing....
>
>Returning to the matter.
>It needs to establish of the rules and of the priorities
>Priority: substance:
>The popup has to show all the information.
>Then you cannot cut the text
>

>width=MAX(defaultpopup.width,combo.width)
>

>
>Rule: Aesthetics:
>it is as in to dress:
>two very different colors can be very well together,
>but two almost equal they often make disgust.
>Then,
>if defaultpopup.width a little smaller is of combo.width,
>then it is worthwhile to apply the rule 1.
>otherwise it is worthwhile to leave it as VFP builds it.
>
>Result:
>

>#define DRESSPOPUPMARGIN 10
>width=IIF(BETWEEN(combo.width-defaultpopup.width,1,DRESSPOPUPMARGIN),defaultpopup.width)
>

>
>The funny one is as to do it!
>How to discover defaultpopup.width?
>If VFP were a true OOP, it would return a contained object in the combo that checks the popup, but it is not this way.
>Then, to do it, we needs to capture the window of the popup with BINDEVENT,
>and to resize it with a few of APIs calls, withou fire some C0005!

Not sure I understand you, but it sure does sound like a very complicated task. It would be great if we can have a combo property DropDownWidth and can manipulate it in run-time.