>>>They want to change the data entry screen to make it easier for them.
>>>The screen will allow entering all times for all employees at a particular location for an entire week in one go.
>>>
>>>So they'll select the Location and the date of the Monday of the week, all the employees scheduled to work at this location for this week will be displayed in a grid with the following columns:
>>>
>>>Employee, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday and some other columns again not that relevant. In each of the day columns they want to be able to enter the start and end time.
....
>>>What do you all think? Is this a good enough reason to de-normalise?

>>Use denormalized cursor to show data and the user enter information in it.
>>Then when Save is pressed normalize it again :-)
>
>>BTW I have one question what happens if some employee work on one location Monday and other in Thursday?
>
>This does happen. All they do is enter the times in the relevant days for each location.

The others already set you straight on denormalizing the non-data-entry table ;-)
Not knowing the travel time between locations: Person A starts at location A at 8, gets called to rush to Location B at 9, works there till 13:30 and arrives back at A to work the rest of the day. Will earn some double time if there is only 1 begin and 1 end each day at each location ;-))