>>Hi George,
>>
>>I was only trying to point out that there IS some sort of problem with the TreeView node properties once localized. They leave a hanging reference to the TreeView and you can't close your form. I guess my postings on this subject were before M$ personnel took a more active interest in us folks here on the UT. FoxPro is notorious for useless error messages (my alltime favorite: File not found! - Yes, I know you can look at your code to see what file, but it's still difficult if it's a variable's content - just tell me what the hell Fox couldn't find!) Maybe the OS group is taking pointers from Fox on these "less than helpful" errors? < G >
>
>Hi Fred,
>
>I'm sure you're right about the problem, however, I haven't run into it yet. I'd assume that it's because I haven't tried any as sophisticated as trying to recurse one. My usage has been pretty simplistic. I rarely have more than one root, and the SelectedItem property gets me what I want. When multiple items are required, there's generally a combo, and selecting a different root from the combo is used to start a routine which clears the tree and re-builds it accordingly.
>
>I wonder, however, in a situation where Programmer A does a recursive routine that causes the error, and Programmer B writes a slightly different routine that doesn't, where the problem lies. As I'm sure you're aware, recursive routines can be quite difficult to do correctly. Did "A" cause the problem by doing something incorrectly? Or did "B" circumvent the problem by doing so? If "A" did something wrong, then I feel that he's caused his own problems. But if the routine was completely correct, then the problem lies with the control.
>
>In my case (that started this), I did something that you can't do apparently. I don't have a problem with either VFP or the ImageList control. I do wish, however, that the documentation had been such that I wouldn't have run into it in the first place. Hopefully, either the problem with the control will be resolved or the documentation updated. If either of these occur, then I'll be grateful and my trouble worth it.
>
>Regards,


Recursive doesn't have anything to do with it AFAIK. I was trying to add child nodes "on the fly" when a parent node was clicked. Like I said, if you create a local variable reference to a TreeView.Child property, you now have a "hanging" form (sometimes). I was only creating this local variable to reduce the typing involved with my code, no recursion. Doesn't make much sense to me!