Adding timesheets via database to MSP 2003

[Mike]

Question for the 2003 experts.
I'm finding a strange issue, if I add timesheets to an existing project on a
fixed work task - It seems that Project then recalculates the work field. Is
there anything specific that would cause this? (It's also modifying
duration, but that's ok)

If I want to add Timephased data/Timesheets to a project, is there anything
I should be careful about touching/not touching? Does MSP store data in the
MSP_Timephased table that could cause problems if I delete and repopulate the
table with timeshoot rows of my own?

 

[Rod Gill]

Hi,

That is an area I found very confusing. You need to understand that Project
only fills the timephased table for reporting purposes and only reads any
data in it if the appropriate flags are set (see pjdb.htm). Normally all
timephased data is stored in binary blobs (no schema available).

In the end I found it was easier and much more accurate to use VBA to update
Projects in Project pro. The same code works for 2007 whilst the update
database code won't.



--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com

 

[Mike]

I understand - I'm making sure the "expand timephased data in database"
option is used.

I think I know why it's been changing WORK - because I've been sending over
% complete as well (in the summary tasks), which sets duration, and work just
gets processed last and recalculated.

however, for some reason if I DON'T send over % complete, my actual hours
change. (Even if I do not set duration or units)

I have not looked into VBA to update Project - is this something I could
build fairly quickly to simply import timesheets?

 

[Rod Gill]

How quickly is completely dependant on your VBA skills! My book has the
basics of how to do it, but the devil is in the detail of handling poor data
and people who assign hours to summary tasks or tasks they are not already
assigned to in project etc. etc.

So, the basic code is straightforward, the final product is only likely to
be done once experience is accumulated of handling the exceptions.

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com