[AccessD] Design shenanigans

Anita,

That's why, when I designed a work tracking system for my current contract,
I didn't allow sub-projects.  I have projects and tasks.  Tasks can have
child tasks which point back to their parents, and a top level task doesn't
have to be linked to a project at all.  However, the client also has work
requests, and we decided that those had to be created from a task level.

Charlotte


On Wed, May 7, 2014 at 12:36 AM, Anita Smith <anita at ddisolutions.com.au>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
>