Previous submitted actual work hour changed

[ch]

something happend to microsoft project and almost all the previous submitted
actual hours for the previous weeks are incorrect. It got weird decimals in
actual work hours and planned work hours.
can anyone please help?

 

[Mike Glen]

Hi ch,

Welcome to this Microsoft Project newsgroup

It sounds like corruption to me. Try the suggestions in FAQ Item: 43. File
Bloat? - Might be Corruption.

FAQs, companion products and other useful Project information can be seen at
this web address:http://project.mvps.org/faqs.htm

Hope this helps - please let us know how you get on

Mike Glen
Project MVP

 

[ch]

Hi Mike,

thanks for help
i tried the method in FAQ Item: 43
seems like its not corruption.
nothing happened.
any other possible ways that i can fix this?

thanks!

 

[Mike Glen]

I don't know Perhaps you could could give us more details. What Actual
Hours were entered and what happened? Do your calendar working hours match
those in Tools/Options.../Calendar tab? What version of Project are you
using? Do you use a server? Does this happen on other projects or other
PCs?


Mike Glen
Project MVP

 

[St Dilbert]

Just a thought:
Assuming by "actual hours" you mean "actual work"?
Was the task still in progress?
Is tools/options/calculation "actual costs are always calculated by
MSP" on (default)?
Then did you update a duration field on that task like "%complete"?

 

[Jim Aksel]

Actual Work is a "value field" not a "time card" or cost field. If you
update Actual Work you are changing %Complete and remaining work. The fields
Actual Work, Work, and Remaining Work all function together. Work=Actual
Work+Remaining Work.

So, if your guys tell you their "Actual Work" on the project this week was
32 hours they are probably telling you "I cost you 32 hours this week" not "I
accomplished 32 hours of progress". For example, if you have a 40 hour
task and they tell you 75% complete and I worked 32 hours.... the actual work
was 75% of 40 hours = 30 Hours. The ACWP was 32 Hours (times rate).

Maybe I'm way off topic... but I hope it helps. Your "Actual Work" will
change when changing the %Complete (or %Work Complete) fields.

 

[St Dilbert]

This will sound a lot like splitting hairs, but there are important
details:

The work fields will always be connected:
Work=Actual Work + Remaining Work; %work complete=Actual Work / Work

As will be the duration fields:
Duration = Actual Duration + Remaining Duration; %complete=Actual
Duration / Duration

BUT when you take a very close look work and duration are NOT ALWAYS
connected!
1. In planning (no actuals yet) once there is an assignment on a task:
work = units * duration. Always connected - that's what you want your
scheduling tool to do.

2. In progress/tracking: different story.
Work and duration are connected when
Tools/options/calculation/"updating task status updates resource
status" is selected and they are disconnected when that option is
deselected.
In the latter case %complete will NOT change when entering actual work,
but %work complete will, of course!

Just try it on a single task project. Whether you want them connected
or not in tracking is a matter of how you really want to investigate
progress and your reporting and project culture. I'm all for
disconnecting them and interpreting Actual Work as timecard hours and
thus as cost. Jim Aksel has excellent reasons for going the other
route.

So give it a try and let us know what serves your world better....

 

[Dave]

Are your calendars consistent across the resource pool and project
files? I have seen something similar when there has been a mismatch in
calendars and working time.

Dave