[AccessD] Design shenanigans

Gustav,
Sounds like a plan that could work.

I'll sleep on it.

Anita Smith


Hi Anita

As you probably will need much the same info for projects as for subprojects, I would have just:

Projects
....Activities

Then have a field in Projects to specify the ID of the parent project - will be empty for parent projects.
I think this what also Stuart had in mind, though I see no reason to google on that.

/gustav

-----Oprindelig meddelelse-----
Fra: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] På vegne af Anita Smith
Sendt: 7. maj 2014 09:36
Til: Access Developers discussion and problem solving
Emne: [AccessD] Design shenanigans

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