>>George,
>>Kenneth is correct, ANY local variable reference to one of the TreeView node properties (FirstSibling, Next, etc.) cause the problem. At the very least you get the "hanging" form that can not be closed, just like a dangling object reference. No amount of NULLing, RELEASEing the variable helps. Sometime the form hangs, sometime you get the C....5 problem.
>>
>>PS:
>>I had posted a thread on this quite a few months ago...
>
>Hi Fred,
>
>I wasn't questioning whether or not Kenneth was correct. However, when I posted the original message it was not only to point out a particular "gotcha", but also to draw attention to that fact that sometimes we're the cause of the problem, and not VFP. The reason I asked was to try to determine whether or not this was the case here.
>
>Of course, if we got more information than "C0000005 Fatal Exception Error" as a message, it might be a bit easier to segregate these.:-)

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 >