>>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.

Yeah, I finally opted for mover-type list boxes, double-click to move individual items, plus command buttons to move single or all items. This "seems" to be fairly "Windows-like". However, I have had to put a lot of time ( finding out why it wouldn't work in the first place, then finding a viable workaround ) on this. Re Jim's replies, I don't know about MS's "strategy" either, but I woul like things that are supposed to work, to work. Reminds me of my Cobol days . . . lot of people bad-mouth Cobol, but I could write programs that would do quite sophisticated things, but would run virtually forever w/o breaking. Don't get me wrong, I love VFP and the neat things we can do with it and similar products. But I DO prefer that things do what they are supposed to do :-).

Bill