Arthur Fuller
fuller.artful at gmail.com
Fri Jun 18 13:12:19 CDT 2010
This problem has been addressed by multiple authors, including my partner Peter Brawley and me, but more leading lights (Celko, Date, et. al.) have also touched this. For our solution, visit www.artfulsoftware.com and look for "trees" on the SQL page. Hope this helps, Arthur On Fri, Jun 18, 2010 at 2:02 PM, A.D. Tejpal <adtp at airtelmail.in> wrote: > Typical fields for a table having hierarchical list of assemblies and > parts are observed to include: ItemID, ParentID, Description, Qty > > With this arrangement, the complete hierarchical chain from each topmost > item (having no immediate parent) downward can be worked out right upto the > lowest part (having no child). > > In situations where a part with same ItemID is needed for more than one > Item chain (i.e. more than one top parent), the above table structure might > not prove adequate. > > Any suggestions - while retaining its role as a self contained table ? > > Best wishes, > A.D. Tejpal > ------------ > -- >