I am glad that you share my feeling that this should work, but it just does'nt here in my code.

Doing more trouble-shooting I also discovered that if I put in a debugging breakpont in the request_delete of the DD and just press F5 to continue then data for the new currentTreeItem is actually loaded into the DD and displayed in DB-aware objects, but when I remove the breakpoint the problem is back Again. A bit spooky!

The good part is that I think I have solved the problem: the "request_delete" is initially sent either to the treeview or some of the DB-aware objects. If I catch the message there and delegate send it to the DD, I can put the code to find the new currentTreeitem after the delegation, and this Works. Maybe not the most elegant solution, but still a solution.

The DD's saves a lot of programming time, but every once in a while they balance the score, by doing something like this :-)

BR
Carsten