Here is a little puzzler that's been in my mind for years. I don't do much with Access, other than poke around and look at samples.
I've never seen anything like my solution (in an old super-mini database application) in Access.
The idea is to create one table that can replace dozens or hundreds of sub tables to a primary table.
By primary table I mean something like Customer, which might have a sub table of Territory (which is actually one level up the hierarchy).
Much is explained in the two files attached in .zip file.
Thanks in advance if you can find a simple and elegant solution within Access or with code.
GrpTest1.zip