Hi Del,

If you open both documents and press Alt-F9, the field coding they use wll be displayed. In the first form I posted, each date that was calculated use a full dat calculation field, just as the first one in the second form's table still does. I've simplified the 2nd-6th fileds in the second form's table by picking up the first one's julian date calculation, but that's not especially important. The real difference is that each of the calculation fields now uses a different set of bookmark names (created by the SET fields) for key parts of the calculation. That way, there's reduced cross-over of the calculations between the fields.

The signature date could be gathered by a formfield with an 'on-exit' macro that locks it after a valid date has been input, but then you'd need the supervisor's macro security set low enough to allow the macros to run and they'd need to either allow macros to run in each & every timesheet or open them only from a trusted location. Once you do that, though, every user is liable to get the macro security warning when the open the timesheet. There are possible workarounds in which only the supervisor has the macro, but implementing such a scheme would be somewhat problematic.

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]