>Is this in VFP5 or in VFP6? We had this problem in VFP5 TreeView and the problem stemmed from accessing any of the nodes (like ChildNode, etc.) in code. As long as we referenced all nodes with the complete hierarchy or using the .Nodes(index), there was no problem. This did not appear to be a problem with the TreeView available to VFP6.


Thanks for the response. I am using VFP6 SP3 with Treeview 6.0 and still have problem after I access the .nodes(index)

Any more ideas?

I will also try to look for outstanding objects as suggested by Barbara.

Regards