[AccessD] Design shenanigans

I think this depends. What are sub projects anyway and why are they needed?
I have never heard of them. Are they just groups of activities into project
milestones?

A slight digression, does anyone know what to do when Lean dictates that a
single activity or group of activities benefits several projects? For
example, hiring interns, bid process, Franchisee Marketing campaigns,
production of user manuals, etc. This would make the WBS a challenge, no?
On May 7, 2014 1:21 PM, "James Button" <jamesbutton at blueyonder.co.uk> wrote:

> Then again, is there a substantial advantage in processing etc, to having
> the
> project and subproject levels when you could have a single table with a
> code of
> (say) 000 to indicate that the entry is a 'project' level one and just
> treat all
> entries as subprojects with reporting processes summarizing as needed.
> Or if using subprojects, then I would expect you to have some means of
> ordering
> the subprojects, so use the lowest possible ordering code (maybe null) to
> indicate that the entry is the only one in a project, and start multiple
> ones
> with the next code
>
> JimB
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
> Sent: Wednesday, May 07, 2014 4:09 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [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
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>