>
> Hi Quintin,
>
> The previous guess was assuming that ListBox Container control containig some custom code to fill the two ListBoxes depending on the current Form.DataEnvironment aliases content, and that one getting triggered in the ListBoxContainer.Refresh() as a kind of VFP standard.
>
> The second option in my opinion would be guessing the relevant VFP custom code, perhaps also being able to disable the ListBox controls or put a transparent Shape on top or so, is not all encapsulated inside the Control itself but maybe partly running in other (Form) methods, so that parts of it may perhaps not run when the Container's parent Page is getting activated, and/or that custom code possibly containing buggy assumptions about the Control's Parent object or similar.
>
> Assuming VFP's native Page(Frmae) control being buggy in that context does not sound likely to me since for one I don't remember any evidence, self-experienced or in the Fox Community exchange - especially when there are no "ActiveX" UI elements involved, and no Win32API painting-controls attempts
>
>
>
> hth
> -Stefan
Hi Stefan,
I use the native PageFrame control, so no custom code there. I have found that I can use the keyboard to navigate and select items in the listbox control. It's only the mouse that's having issues, which I find very bizare.
Thanks,
Quintin