You're getting one large chunk, because your resource is probably allocated
evenly across an assignment. The MSP_Timephased table appears to save to
the largest unit (TD_Units field) possible.
To see this behavior:
1) Make a new schedule
2) Enter 1 task, with a ten 10 day duration, and assign one resource to it
3) Turn on the Extend Time phase option
4) Save the file to a database.
5) Open the database and view the MSP_Timephased table (there's 1 line)
Now, change the resource allocation across the assignment
1) Make a new schedule
2) Enter 1 task, with a ten 10 day duration, and assign one resource to it
3) Open the Resource Usage view and set the timescale to display days
4) Set the resource's assignment hours to 4, for each of the days in the
first week (leave the second week's assignment at 8hrs)
5) Turn on the Extend Time phase option
6) Save the file to a second database (don't save to the same database -
it's easier to see this if the files are separate)
7) Open the second database and view the MSP_Timephased table
See the difference? Look at the number of rows, the TD_Start, TD_Finish,
TD_Units, and other fields.
DeanD said:
Just to confirm:
I currently have a global resource pool that has around 30 linked
projects. When I open the pool, I open all of the linked projects inside a
temporary project i.e. Project2.mpp.
I would like to export the work for a selected period i.e. start to end of
this month (which I can do), but I would like each week separated into
different fields i.e.
Task Week 1 Week 2 Week 3 Week 4
Design 45 50 60 70
I have a timesheet database that captures actual hours, so I would
ultimately like to replace each week with actual hours to allow me to track
the progress of a project across a month.
