If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

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."

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.

MeanOldDBA
derrickleggett@hotmail.com
When life gives you a lemon, fire the DBA.