>I just use the Universal Thread the way it is meant, as a resource... :)

I'm not (yet...) a UT Premier member, so I can't search through previous threads...

>In many ways the OCX control closely mirrors the Treeview common control included with Win95. The treeview common control has no method by which the parent for a node can be changed and therefore the OCX doesn't either. The only way is to delete the current node and children and to reconstruct them somewhere else (just like you are doing.)

Vfp Help files said the Property "Parent" can be also used to set the parent node... Something should be wrong here (help files or treeview).

>I got DropHighlight to work just fine (if Hittest returns an object I set dropHighlight to that object).

Maybe because you're working with Vfp 5.0a (I've informed just a few weeks ago the brazilian M$ about this new release, so that they could start looking for it...)

>I haven't tried creating my own drag image, but I plan on doing so soon. Please be a little more specific on the CreateDragImage issue and I might be able to shed some light on it.

I've tryied to use it the same way it's explained on Help, something like:
Treeview.DragIcon = loNode.CreateDragImage (or maybe loNode is a parameter, sorry but I'm not with Vfp right now...) - it gives an error message (maybe solved in 5.0).

Anyway, for now I've decided to keep the other method for changing the structure (left click, right click), also because I've found out that if I try to Drag a Node to another place which is not visible on the Treeview, it doesn't scroll automatically (it would be necessary to write some code to accomplish that - probably using "EnsureVisible" which also does not seem to work here... What about there?)

Thanks for all,
Renato