Need to change existing design to accomodate more detailed tracking of time Currently I have a relationship between contact and time_log (contact is a verb here - could be a meeting/phonecall/email).  Time_log holds both a date and time, each contact is associated with one date and amount of time spent on that contact.  I also have a list of several contact_services_provided at each contact.  This was fine until I learnt that time spent on each of the specific services provided at a contact was also required.  I thought of linking time_log to contact_services_provided instead of directly to contact, but then the date is repeated for each service provided which is not correct (there should be only one date per contact), so I'm not sure how to proceed.  Also, I've added a sad image of my user interface and associated database design which might help to visualize the problem (you'll have to zoom in...)
Can't see the attachment, but if I understand correctly, any one contact can only have one date. Each contact is made up of (potentially) more than one contact_services, each having it's own duration. In this case, a suggestion would be:

contact_table:
contact_id
time_stamp
duration (of the contact)

contact_service_table:
unique_id
contact_id
contact_service_type_id (or something along those lines)
duration (of the service)


Elaborate further if I am misunderstanding.