Hi,
Using N joins is a first alternative, to get through N generations,
mainly if your table is storing the "ParentID". You can also use Nested
Sets, a kind of pre-compiled hierarchy, but doing so, while it would be
faster, would require a special "design".
Hoping it may help,
Vanderghast, Access MVP
