A combo with lots of items is definitely NOT recommended.

As others have noted, textbox+button+grid can better
accomplish the same thing in such circumstances,
including availability of PEMs and a dropdown appearance that
looks the same as a combo's. Plus you
only really need one such "dropdown grid" object per form
page. Initialize its Visible = .F., load/position/display it
when the button is clicked, set Visible=.F. again
at the top of your process-selection routine.

-m.

===========================

>>>We thought it was our class, but then we threw a default Foxpro ComboBox on a form and set the RowSourceType to Fields, the RowSource to a cursor (tried a table also) and then started playing around with selecting different values. It is 2 column and we can consistently make it break. By choosing a row near the top of the list, then choosing one around number 250 in the list, it will not change the value. If we choose something near the bottom, it will. If we have one chosen at the bottom, then choose one near the top, it will not change the value. We are very tired of testing this, but it does seem to happen more when the display drops "Up" (near the bottom of the screen) then the normal "Down" direction. It seems to only happen when the cursor or table has (somewhere around) 250 records or more. Anyone seen this type of behavior?
>>
>>Use a Browse. No practical limit on the number of records that I am aware of.
>>
>>Peter
>
>But then we lose the needed behaviors, methods, properties of the combo.