>Yes. But not consistently. I.e., You'd click on one page and the two listboxes display, then click on a different page, and then come back and they are gone, then try again, and they are there...That's why I changed to the Activate/Deactivate event of the page to set the visible property of each control Visible or Not Visible. This made each control respond properly, i.e., visiblity, but it still didn't affect the Click event, I still couldn't click on the listboxes.
>
>
Bob, leaves alone Activate/Deactivates, are full of bugs.
This is another bug,
VFP's drawing routines they draw in the buffer,
but they forget him to send the Windows updating
This produce a process timing bug, hard to reproduce in deterministic way
Workaround for this bug
this.Visible = m.lEnable
Thisform.Draw
>
>
>
>>>THANK YOU for the suggestion. But I am afraid it doesn't work. In fact, as I tested it, some of the listboxes appeared at first, then when I clicked on another page and came back they did not reappear.
>>>
>>
>>>So I went to the Activate/Deactivate of each page to set/reset the visible property of the listboxes and still no luck.
>>>
>>>Do you have any other suggestions? What's really weird is I created a test form with the same number of pages and listboxes, and placed each listbox in the same order, then I used a simple query to add items to each list box, and I have no problems. But the form in our application is much more complex, and it has all sorts of objects on it and here's the weirdest part, after I select a listbox on page 5, all of the other listboxes become "clickable". ??
>>>
>>>Any Ideas would greatly be appreciated. I have a 15 year old application with over 100,000 lines of code where this form is a central to the whole app. and I need to be able to upgrade to 9.0 for the new report features... THANKS!! IN ADVANCE.
>>>
>>>Bob
>>
>>Then, confirm this:
>>
>>1. You have Listbox.visible = m.lEnabled on all ListBox's UIEnable() event
>>2. When you return to the page all the page's listBox still not visible
