Maybe, but in the final analysis, it's likely that you'd still have to iterate through the array at some point for multiselect listboxes.

The operation might run a bit more quickly because the array would normally be shorter, but overall, the code you'd have to write wouldn't seem to be that much different (if at all). So I'm not sure MS would think it worth spending a lot of time on.

Having said that, it would certainly be useful in non-multiselect listboxes where you'd know that the array only had one element. Is it worth the time for MS to do it? I think it might be hard to justify for a couple of lines of code.

Alan

>>Yes, I took that as a given.
>>
>>My reference to multiselects to Nadya was just part of the conversation about how one finds what is selected in a list box, and my feeling that it is not out of line to have a consistent approach regardless of whether the list is a multiselect or not.
>>
>
>I'm thinking, that some internal array property of selected items would be nice. Just curious, if you see it reasonable enough to add to the VFP Wish list?