Hi,

Someone at microsoft.public.project.pro_and_server thought that I might
have more luck here. So here goes...

I'm trying manually insert some actual work for an assignment into the
MSP_TIMEPHASED_DATA table.  This assignment already has some actual
work recorded against it.

For example, to do this I make a new record in the table with the
following data:

PROJ_ID = 1 (the project id)
TD_UID = 1 (a unique id)
TD_FIELD_ID = 2 (actual work)
TD_CATEGORY = 3 (category = assignment)
TD_REF_UID = 1 (the uid for the assignment)
TD_START 10/06/2003 09:00
TD_FINISH 11/06/2003 17:00
TD_UNITS 2       (days)
TD_VALUE1 300000.0  (5 hrs)
TD_VALUE2 180000.0  (3 hrs)
TD_EXT_EDITED 1

I also set PROJ_EXT_EDITED=1 in the MSP_PROJECTS table.

When I then view the project in Project the added time is in the
correct place and all is well.  The problem that I have is that
when I save the project back to the database. The above entry
in the timephased data table is replace by another one with the
following properties.

PROJ_ID = 1 (the project id)
TD_UID = 1 (a unique id)
TD_FIELD_ID = 2 (actual work)
TD_CATEGORY = 3 (category = assignment)
TD_REF_UID = 1 (the uid for the assignment)
TD_START 13/06/2001 09:00
TD_FINISH 11/06/2003 17:00
TD_UNITS 8       (days)
TD_VALUE1 0.0
TD_VALUE2 480000.0  (8 hrs)
TD_EXT_EDITED 0

It has changed the units from days to years so I seem to have lost
information on when the actual work was performed.  From the entry
above alone I no longer know on what days the 8 hours work was
performed on.   When I open the project up in project again it still
knows what days the 8 hours is spread, but I'm pretty sure that
project gets its info from the large binary blob in the msp_projects
table.

This only seems to happen when there is a large gap (say 1 yr) between
the new entry and the last time that actual work was recorded for the
task.  I have tried padding the gap between the two entries with zero's
for actual work - in order to cause a split in the task, but this does
not help.

I would like to be able know what days actual work was performed on
for each task from the information in the database.  Has anyone
encountered this behaviour before, or have any information that might help?

Cheers,
Greg