DBTreeView does not work properly when a related record is “deleted” or moved.
For example, take a tree with a node and a leaf under it. Now delete the leaf record from the database and look at the tree. Nothing happens. Then close and reopen the parent node and you will see that the leaf item is still present but without a name. This shows that the tree is dynamically updating the name, but not the structure. Showing a node or leaf that doesn’t exist and with a blank name is a problem.
When you try moving a node/leaf, the leaf/node does show up under the new location automatically (this is the dynamic behavior we need everywhere), but it still leaves the orphaned nameless item behind. Inserting a new record does nothing at all.
Yes, reinitializing the tree does correct the structure, but this leaves all the nodes closed and is unacceptable for obvious reasons. There is a request for a refresh tree feature, but the above seems to be a bug in what we already have. The tree does update the name of a node/leaf when deleted, so shouldn’t it also know when a leaf/node is deleted?