I'm unaware of any way to adjust that. Different organizations define their
fiscal week 1 differently. For some it's the week containing Jan 1, for
others it's the first full week in the year, for other's it's the week
containing Jan 1 unless that week contains less than 4 days in the new year
and then it becomes the following week, and there are probably other schemes
as well. As far as I know, with Project it's the first full week in the
fiscal year and there's no other options available. In defense of that,
since Project's basic job is to come up with a task schedule to be worked by
the resources and an estimated budget for the same it's not usually that
crucial an issue. Most people ( ie, your resources) use the normal civil
calendar in organizing their daily lives (even if their accounting
department uses the fiscal calendar). Since it's not an accounting
application anyway, does it really matter if the cost estimate of a resource
doing a task of December 29th gets charged against fiscal 2004 or fiscal
2005 in the project's budget estimates? When the work is done and the
actual timecards, invoices, checks, etc are massaged by the actual
accounting programs you use for general ledger, etc, they're going to get
apportioned to the right bucket anyway. Project's numbers, even actuals,
are really only estimates to a close approximation at best. In other words,
don't worry about it, a year from now no one will know the difference or
likely care one way or the other <grin>.
Rule 1 - don't sweat the small stuff. Rule 2 - most things are small stuff.
<grin>
