[AccessD] Design shenanigans

Classic Bill of Materials problem. You can have more than 3 levels in some situations with 
links between various levels.     There are several approaches, a common one is to use a 
field to indicate what level the item's parent is and work with Union queries to get the relevant 
children for a given parent.

 A google on "BOM schema"  will probably give you lots of ideas.

-- 
Stuart

On 7 May 2014 at 7:36, Anita Smith wrote:

> I have a small design problem that I thought I might throw out there
> to see if anyone has a solution:
> 
> It goes like this - I have the following tables:
> 
> Projects
> ....Sub Projects
> ..........Activities
> 
> The problem is that not all Projects have Sub Projects so the
> Activities could be linked directly to the projects table as well as
> the Sub Project table.
> 
> My initial thoughts are that each project would need at least one sub
> project - i.e. the 'forced' sub project is used only to link over to
> the project table. 
> 
> Now that I think a bit more, I'm not really liking that idea.
> 
> What to do .... what to do?
> 
> Anita Smith
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>