MPS 2003 changing Actual Time

[Mike]

So - if I have an apllication that manually enters task, assignment, and
timephased data into the database - what would cause Project profesional to
change the actual work, and add values onto the timephased data?
Data in the db looks good before it is opened in Professional - once I open
it in Project Pro, additional rows get added on.

is there an internal calculation somewhere I should look for?

 

[Rod Gill]

Hi,

Directly editing data in the Project Server database is not supported by
Microsoft and there is no documentation that gives us all requirements to do
so for Project Server 2007 databases. The only supported way of adding tasks
to a Project are VBA and PSI.

You could create a new project using xml or Excel then import it into
Project Server.

Project Professional is obviously not receiving what it expects, so is
re-calculating to avoid conflicting data.

--

Rod Gill
Microsoft MVP for Project

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

 

[Mike]

Yes, I'm aware, for the Project 2007 version we'll be using the API's. My
issue is that I inherited this application for the 2003 version that we have
to use until the 2007 version is finished.

Is there any documentation or information perhaps on what fields I should
avoid changing when adding tasks/timesheets? I found Clearing out the
ASSN_ACT_WORK field helped on the initial push of data, but the issue still
seem to crop up when the project is saved in Project Pro, more data is added,
then reopened in Pro.

Guess I'll just experiment around with it.