>John:
>I'm not certain what flicker you are seeing. My app has a pageframe with 3 pages with different ways of accessing the same reports. When my user adds, deletes, or renames a 1st level or 2nd level node, I use the -1000 to improve performance and eliminate the visual manipulation of the tree. I started out rebuilding the tree from the tables each time any of these changes occurred. We decided to try to just manipulate the tree by changing the "keys" in the asscoiated array, deleteing the node (under all manipulations) and adding it back. I needed to have the tree "sorted" without regard to case, so I had some additional problems.
>
>We have at least 100 nodes on most pages, and none of the testers have commented on Flicker (and since something off by 1 pixel (in their opinion) generates a "bug") I'd expect some comment.
>
>Good Luck with the treeview. I spent over 6 weeks on a daily basis tyring to figure out how to implement the designer's interface and now that I'm a "expert" (drip under pressure), I'm glad to be "done" with it.
>
>Mike
The flicker was from because I did this:
_thisform.lockscreen = .T.
this.olist.visible = .F.

** add stuff
_thisform.lockscreen = .F.
this.olist.visible = .T.

I think the visible caused a flicker

Thanks
John