Timephased Data Problems

[Theresa Fitzpatrick]

Hi,

I've seen similar problems posted here, but I haven't seen
any resolutions. Can anyone shed any light on this
problem for me?

Here's the situation:

I'm programatically updating the msp_timephased_data
table, and everything seems to work OK most of the time.

However, sometimes, I'll insert a row with this
information into the msp_timephased_data table:
TD_Start: 4/4/2003 8:00:00 AM
TD_End: 4/4/2003 5:00:00 PM
TD_Units: 2 (days)
TD_Value1: 480000
TD_Value2-7: all 0
TD_EXT_EDITED: 1

(and I set the Proj_Ext_Edited flag in the MSP_PRojects
table to be 1, also).

But when I open the project in Project 2002, it shows the
time that I've entered split across 4/4 (a Friday) and 4/5
(a Saturday). But only sometimes, not all the time. I
ve tried checking the resource and task calendars, but I
don't see anything odd there.

Also, if anyone enters time manually for an assignment
through the project interface, sometimes it doesn't seem
to show up in the msp_timephased_data table, but still
shows up in the project task view.

But not all the time, only once-in-a-while.

In a nut-shell, it seems that MSProject is taking the data
I enter in the MSP_Timephased_Data table and doing
whatever it wants with it. Why???

Any ideas? Has anyone run across this before?

 

[Rod Gill]

Hi,

Create a task that starts on Friday and finishes Monday (with an assignment)
and look in the timephased table to see how it's stored. Timephased data is
a pain in the but and to read it accurately you need to read the calendar
table as well to determine the non-working periods.

--
Rod Gill
Project MVP
For Microsoft Project companion projects, best practices and Project VBA
development services
visit www.projectlearning.com/