>Ok, I'm grasping at straws. I've got a combobox drop down list that evidently has too many entries in the list (~1850). I had incremental search turned on so that the user would go to the area of the list they were interested in as quickly as possible. However, what's happening is that I'm hitting some sort of page fault (GPF) roughly 2/3 of the way through the list (if the user picks that entry during an editing session(controlled by the button bar)). In other words, any of the items above this mark or below this mark won't trigger it. Is there a better or more elegant solution anyone can suggest besides breaking the list into little pieces and writing code to see what letter the user enters and picking the appropriate sub-list? Thanks!
>
>Laurisa Watkins
>Seattle Parks Dept.

Laurisa,
Ed Pikman's message covered the 'bug' with the 253 + 256*n items. I've found that for large numbers of items a grid with an accompanying text box is a good replacement. Use the InteractiveChange event of the textbox to update the grid to show the closest item entered.

If you need to pick multiple items from a grid (as with the MultiSelect property on a list), add a logical field to the cursor populating the grid and put a checkbox in the grid for that field.

HTH
Barbara