>>George
>>
>>>> I was asking which one was dropped on the form first. The ImageList or the TreeView? <<
>>
>>Originally the Treeview, then the Imagelist.
>>
>>However, I pulled the treeview and replaced it with a Sheridan treeview. That still had the error, so I replaced it the MS Treeview again.
>>
>>So, I guess you could say I've tried it both ways.
>
>It's always been my practice to make sure that these sorts of objects are created in a specific order. For example, say I want to have a TreeView load pictures from a ImageList which gets them from a PicClip control. I create the PicClip first, the ImageList second, and the TreeView last. This was when the parent form is instantiated, the PicClip initialize first, then the ImageList, etc. Saves lots of headaches.

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...