Well, since you can't really edit a listbox without some sort of code adding or removing elements in the list, I would consider the listbox "read-only" by default. The truly read-only state would essentially disable the code that adds and removes items from the list, not the listbox.

I think that KMoverObj supports this except when the DblClick event of the listbox fires. This event subsequently calls the MoveOne or RemoveOne method. This read-only state could just disable those calls.

>Doug,
>
>>Hey, wouldn't this security enforcement be better served somewhere other than the When event of the list? My reasoning, is that by returning .F. in the When, the user won't be able to scroll the list. I think the Mover needs to be read-only, not the lists. You can probably just do this in the MoverContainer's MoveOne, MoveAll, RemoveOne, & RemoveAll methods.>
>
>Actually, this really boils down to a question of how to make a list box read only. What are your thoughts on this?
>
>Regards,