Return All Nodes In Many-to-many Hierarchal Tree
Solution 1:
For SQL Server: Adjacency list vs. nested sets: SQL Server
For Jet/MS Access, recursive queries are not an option, so nested sets would be the way to go. For a sample: http://www.mvps.org/access/queries/qry0023.htm
Some background on nested sets:
To implement a nested set solution you would need to add and maintain two additional columns in your table: Lt and Rt(left and right, respectively). You populate these columns by executing a modified preorder tree traversal to assign values to these columns. This can be done most easily with a recursive function. You can then use the left and right values to determine descendants at SELECT time.
The tradeoff is more processing required whenever data is changed but much faster execution when data is retrieved.
The concept is somewhat non-intuitive and certainly has a learning curve, but I have personally used it to great effect. As far as I know, it is the only way to accomplish what you are after using only SELECT queries in Jet (the MS Access db engine).
Sample Nested Set Answer :
ParentID ID Lt Rt RowNumber(Reference)
Null 11180122131243102434933556416141756715166281112739788Then to get all descendants of ID 2:
SELECT*FROM Tbl WHERE Lt Between2And13Here's what the tree looks like graphically:

Solution 2:
Since you need to model data where nodes can have multiple parents, a nested set/MPTT solution will not work. Another alternative is the use of a closure table.
You would create an additional table that held pairs of items for every ancestor's descendant (and vice versa):
AncID DesID 1 2 1 6 1 4 1 8 1 7 1 3 1 5 1 9 2 4 2 8 2 3 2 5 2 9 4 3 4 5 4 9 3 5 3 9 6 7
Then you would use a join to get the items you need:
SELECT*FROM Tbl INNERJOIN Closure ON Tbl.ID=Closure.DesID
WHERE Closure.AncID =2
Post a Comment for "Return All Nodes In Many-to-many Hierarchal Tree"