Bruce (and Bill),

This looks more and more like a "strategy" by MS - pretend that we have all knids of capabilities available to us, but in fact only one or two ACTUALLY work. Write up some KB articles gently pushing us to the lone way that works and, voila, no longer any "need" to provide the missing functionality!
This may also be why MS is so tight-lipped about telling us what "fixes" it has implemented in interim releases. Possibly, in many cases, it prefers to keep the impression that something is still "broken" so that fewer people will actually use it.

It brings me back to the topic of a few weeks back - lets get what we have WORKING PROPERLY **BEFORE** we get on to new functionality (i.e. more, but newer, BUGS). Let's *PROPERLY* document what we already have!

Cheers (yea, right),
Jim N

>>Once again ( sigh ... ), for those interested, I tried the workaround for the second item and it works for a single-select listbox but not for a multi-select listbox. At this point I guess the only solution for multi-select case is a mover-type list box.
>>
>Just thought I'd mention that we've been through some of these problems too, and decided that wherever possible, to just use single click listboxes instead of multi-select. Just click each item once to move from list1 to list2 or vice-versa. The users really like the easy action (easier than movers or multiselect). Of course this only works for certain simple situations.