This seems to work ok, but how can I handle when a non-leaf node
goes back to being a leaf?????? (ie all child nodes are deleted).

How can by 'after delete' trigger determine that nothing else has
parentnode = old.idcode??

Ho hum, SQL Server here I come >:0

John

--- In firebird-support@yahoogroups.com, "johnsparrowuk"
<jsparrow@e...> wrote:

> All I can think of is having another table of 'leafnodeid's.
> Touching the record when a workrecord is created for it, and
> deleting it when a child node is assigned.