>Oh it naturally exists and exists more often than you think (real number is much higher than 1800 in most cases). You shouldn't feel sorry for the end user, because that is exactly what they want. You should be sorry about me, the developer who needs to create effective techniques in such cases.
>
>No, I feel far sorrier for the end user. There is, quite likely, a business process issue here - I would love to hear an explanation why end users need this, without the possibility of saving re-used ilsts and/or selecting smaller parent segments. Odds are good that there's an opportunity for an improvement that doesn't involve code. Developers are sometimes far too eager to try to scale out a solution where the problem exists elsewhere.
>
>Do me a favor....create a large list...and then use the webform/winform as a user....pick 1800 in the scenario you are describing (non-predictive...different scenarios each time, no common pattern of selections), and then tell me what you think.

Kevin,
It is OK for you to feel sorry for whom ever you want. Believe it or not that is the way it needs to be. I don't feel a need to explain the details of application.

I have been doing that for a long time. Let me tell you what I think. It works perfect.

Cetin