Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
other
informationbridge
office.intranets
office.misc
office.setup
office.xml
officeupdate
onenote
photodraw.discussion
powerpoint
producer
proj.standard&server
project
project.developer
project.pro_and_serve
project.server
project.vba
project2000
publisher
publisher.prepress
publisher.programming
publisher.webdesign
visio
visio.createshapes
visio.database.modeling
visio.dev.diagrams
visio.dev.shapesheet
visio.dev.vba
visio.dev.vc
visio.developer
visio.general
visio.installation
visio.printing
visio.software.modeling
visio.troubleshoot
  
 
date: Wed, 2 Jul 2008 10:51:02 -0700,    group: microsoft.public.project.developer        back       


Project Server 2003 changing Actual Work   
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?
date: Wed, 2 Jul 2008 10:51:02 -0700   author:   Mike

RE: Project Server 2003 changing Actual Work   
Changing task status such as % complete on a task can and will change actual 
work depending on the settings that you are using.

What settings are you using for how project calculates actual work?
How specifically are you updating the data? What are you doing about 
remaining work?

There are a large number of factors that come into play. Are you aware that 
it is not recommended to edit the database directly and at least in Project 
2007 even reading the databases other than the reporting database is not 
supported?

-Jack Dahlgren

"Mike" wrote:

> 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?
date: Wed, 2 Jul 2008 11:35:01 -0700   author:   Jack Dahlgren

RE: Project Server 2003 changing Actual Work   
Oh yes - we're working on an API only interface for 2k7.  This legacy stuff I 
just inherited, and am trying to patch it up for a few months until we can 
phase it out.

I think I figured it out, we had apparently been sending total actual work 
over in the assignment row, as well as sending over timesheet data.  Still 
need to test it a bit. I'm not sure at all why that would cause it skew the 
timesheets though.

"Jack Dahlgren" wrote:

> Changing task status such as % complete on a task can and will change actual 
> work depending on the settings that you are using.
> 
> What settings are you using for how project calculates actual work?
> How specifically are you updating the data? What are you doing about 
> remaining work?
> 
> There are a large number of factors that come into play. Are you aware that 
> it is not recommended to edit the database directly and at least in Project 
> 2007 even reading the databases other than the reporting database is not 
> supported?
> 
> -Jack Dahlgren
> 
> "Mike" wrote:
> 
> > 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?
date: Wed, 2 Jul 2008 13:17:25 -0700   author:   Mike

RE: Project Server 2003 changing Actual Work   
Of course, the other issue I'm seeing is when we port over a lot of timesheet 
data (directly into the database), when Project Pro is opened for the first 
time, it takes a VERY long time to load.  It seems directly related to the 
amount of timesheet data sent over, but the "open" time can be upwards of 1-2 
hours.  I'm guessing it's a calculation Project has to do on every timesheet 
- I'm not sure if there's a way to speed it up though.

"Jack Dahlgren" wrote:

> Changing task status such as % complete on a task can and will change actual 
> work depending on the settings that you are using.
> 
> What settings are you using for how project calculates actual work?
> How specifically are you updating the data? What are you doing about 
> remaining work?
> 
> There are a large number of factors that come into play. Are you aware that 
> it is not recommended to edit the database directly and at least in Project 
> 2007 even reading the databases other than the reporting database is not 
> supported?
> 
> -Jack Dahlgren
> 
> "Mike" wrote:
> 
> > 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?
date: Wed, 2 Jul 2008 13:21:00 -0700   author:   Mike

RE: Project Server 2003 changing Actual Work   
It turns out it did not fix the problem.
We're inputting information directly, since we're trying to push over data 
from another software system, so tasks/assignments, and timesheets are put 
directly into the MSP tables.

The first time we put all of the above into project, everything looks good.  
however, once the Project is saved sindie of Project Pro, and subsequent 
attempt to synchronize (using the same methods used for the intial push), and 
actual hours are being modified - it seems they are getting pushed out to the 
project end date.

"Jack Dahlgren" wrote:

> Changing task status such as % complete on a task can and will change actual 
> work depending on the settings that you are using.
> 
> What settings are you using for how project calculates actual work?
> How specifically are you updating the data? What are you doing about 
> remaining work?
> 
> There are a large number of factors that come into play. Are you aware that 
> it is not recommended to edit the database directly and at least in Project 
> 2007 even reading the databases other than the reporting database is not 
> supported?
> 
> -Jack Dahlgren
> 
> "Mike" wrote:
> 
> > 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?
date: Mon, 7 Jul 2008 08:43:04 -0700   author:   Mike

Re: Project Server 2003 changing Actual Work   
You say the project takes a long time to open. This could be because Project 
is finding conflicting information and is therefore stuck in a loop 
re-calculating. In the pjdb.htm file, there is a sequence list of how 
Project calculates data. I recommend you update the minimum information 
required for Project to calculate what you need. Do not enter data that 
Project can calculate for itself.

As this is legacy stuff, have you considered using VBA macros in Project to 
read the data? This may well be much quicker and simpler. The code once 
working could be converted to an Add-in that works in 2003 and 2007.

-- 

Rod Gill
Microsoft MVP for Project

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



"Mike"  wrote in message 
news:8C2F514D-895C-4581-8357-B14F86142711@microsoft.com...
> It turns out it did not fix the problem.
> We're inputting information directly, since we're trying to push over data
> from another software system, so tasks/assignments, and timesheets are put
> directly into the MSP tables.
>
> The first time we put all of the above into project, everything looks 
> good.
> however, once the Project is saved sindie of Project Pro, and subsequent
> attempt to synchronize (using the same methods used for the intial push), 
> and
> actual hours are being modified - it seems they are getting pushed out to 
> the
> project end date.
>
> "Jack Dahlgren" wrote:
>
>> Changing task status such as % complete on a task can and will change 
>> actual
>> work depending on the settings that you are using.
>>
>> What settings are you using for how project calculates actual work?
>> How specifically are you updating the data? What are you doing about
>> remaining work?
>>
>> There are a large number of factors that come into play. Are you aware 
>> that
>> it is not recommended to edit the database directly and at least in 
>> Project
>> 2007 even reading the databases other than the reporting database is not
>> supported?
>>
>> -Jack Dahlgren
>>
>> "Mike" wrote:
>>
>> > 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?
date: Tue, 8 Jul 2008 10:37:53 +1200   author:   Rod Gill rodATproject-systemsDOTcoDOTnz

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us