>I have a form with a number of controls (comboboxes and listboxes) which is used to populate a table (that is control-source for these controls). PROBLEM is that form's response is VERY slow because of size of ROWsource for two comboboxes on form. (Rowsource is a table of about 2,000 records.) Slow behavior exhibits both upon creation of form and upon interactive drop-down of combobox list.
> The rowsource table is included in the forms dataenvironment, and is indexed (regular) by the fields used as rowsources in the combobox. I've tried using rowsourcetype-6 (fields) and specifying the to-be-displayed fields in the combobox's rowsource property, and I've tried rowsourcetype-3 (SQL-select) and selecting to a cursor in the rowsource property; both yield similar, SLOW results. There is no filtering involved -- all records are being shown.
> Users will need to use the combobox control every time they use the form, so a workaround suggested in MS' DevGuide -- viz., setting the rowsource dynamically in the gotfocus event, rather than statically -- wouldn't be of much use.
> Any suggestions?

Common wisdom is that's *way* too many items for a combo, a couple hundred is the most that can ever reasonably be used. I've found performance trouble at about 300 or so, myself. You'll have to look at other solutions, like a textbox to filter the combo input, something like that. If you have real estate problems, think about pages or a popup modal with a grid, maybe.