RE: How do I handle this??
- From: mauricio <mauricio@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 5 May 2008 05:52:00 -0700
I also have another question. This is my basic database design and I want to
see if I am taking the right approach.
1. Projects Table: Main table, contains start date, end date, projmgr, etc.
- details about project (key: projectid)
2. Project Ranking: Project Ranking in 6 categories and total rank score
(key: projectid)
3. Project Resources: Which resources are assigned to this project (key:
projectid)
4. Project Updates: Weekly update for each project (key: projectid)
5. Project Issues: Issues for each project and details like date, owner, etc
(key: projectid)
6. Employees: A list of all employees who work on the company and could be
the resources assigned to a project. (key: employee id)
Let me have it!!! How badly designed is this database??? I also don't know
how to relate the tables.... Please help!
"mauricio" wrote:
I have a "projects" database. I need a UpdateStatus field on my table so the.
users can enter weekly updates on their projects. I need to be able to keep
these updates for 52 weeks. I also need to timestamp their entries. Not every
project will have an update everyweek.
I created a table like this. (I already have a Projects Table, with all
other details about the project, ProjectID is the key for that table)
ProjectID update1 update2.............update52
Is this the best design for this?? If it is, how do I get the timestamp for
each entry?
- Follow-Ups:
- RE: How do I handle this??
- From: Duane Hookom
- RE: How do I handle this??
- References:
- How do I handle this??
- From: mauricio
- How do I handle this??
- Prev by Date: How do I handle this??
- Next by Date: RE: How do I handle this??
- Previous by thread: How do I handle this??
- Next by thread: RE: How do I handle this??
- Index(es):
Relevant Pages
|
Loading