:) Happens to all of us. You might even shorten the code :

*--cmdAdd Button click
*--Adds an item selected in lstSource listbox to lstSelected listbox
THISFORM.LockScreen = .T. && Is this really needed - not sure when it's not grid :)
with THIS.parent.lstSource
 if .ListIndex > 0
   THIS.Parent.lstSelected.AddItem(.List(.ListIndex))
   .RemoveItem(.ListIndex)
 ENDIF
endwith
THISFORM.LockScreen = .F.

Cetin


>This is too cool Cetin! It works great. Now I can select an item in the left listbox and copy it to the right listbox and there is not delay because I am not stepping through the listbox to determine which item is selected. Can't believe I forgot about listindex! Haven't used it in months....THANKS!
>
>
>

>*--cmdAdd Button click
>*--Adds an item selected in lstSource listbox to lstSelected listbox
>THISFORM.LockScreen = .T.
>nCnt = THIS.parent.lstSource.ListIndex
>IF THIS.Parent.lstSource.Selected(nCnt)
>   THIS.Parent.lstSelected.AddItem(THIS.Parent.lstSource.List(nCnt))
>   THIS.Parent.lstSource.RemoveItem(nCnt)
>ENDIF
>THISFORM.LockScreen = .F.
>

>
>>>When I click on an item in a listbox to select it, I am storing the value in the listbox to a variable. I would also like to store the listbox item number to a form property to determine which item was selected instead of stepping through the listbox as it is now (see code below). In other words, I do not allow multiselect on the listbox and I want to know what the 'nCnt' (see nCnt var below) value is when I click on an item. Is there anyway to determine that?
>>>
>>>

>>>nCnt = 1
>>>DO WHILE nCnt <= THIS.Parent.lstSource.ListCount
>>>   IF THIS.Parent.lstSource.Selected(nCnt)
>>>      THIS.Parent.lstSelected.AddItem(THIS.Parent.lstSource.List(nCnt))
>>>      THIS.Parent.lstSource.RemoveItem(nCnt)
>>>   ENDIF
>>>ENDDO
>>>

>>
>>Directly use ListIndex.
>>Cetin