Results 1 to 3 of 3
  1. #1
    Join Date
    Jun 2004

    Unanswered: Just A simple Question

    this a long ending debate between a friend and me.... following up with the example of the database that i posted earlier today.... i have another incury to you guys...


    This is how i understand it... an employee has a project, therefore the project has a timer, status and activities.... am i correct?

    what my collage was implying is that the employee has the project and the employee has the Timer, and ProjectStatus and the Aactivities....

    Who is correct in this one? this is a long ending debate

    can anybody help us
    Last edited by Aleman; 06-30-04 at 16:11.

  2. #2
    Join Date
    Jul 2003
    San Antonio, TX
    I'd say bofem (both of them). Each Employee has to have a timer to track his/her involvement in the project. Each Project needs a timer to track its duration. If you rely only on Employee's timer, then the total amount of time may be in hundreds of years and you total everybody's time, simply because more than one employee can potentially work on the same project.

    If, on the other hand, you choose to rely only on Project's timer, you will not be able to account for each employee's contribution to the project, thus - firing may start
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

  3. #3
    Join Date
    Apr 2004
    Kansas City, MO
    I agree. If you don't design this upfront, you will end up doing it later. You also might want to be able to say an employees attributes are attached to certain elements of a projects attributes. That would be a real fun design. Then you throw templates into the mix. Great fun.
    When life gives you a lemon, fire the DBA.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts