Re: Trying to understand MSP 2003/2000 behavior

Tech-Archive recommends: Speed Up your PC by fixing your registry

In article <O20NZrUlHHA.1624@xxxxxxxxxxxxxxxxxxxx>, "Mike Glen"
<glenATmvps.org> says...
Hi David,

Welcome to this Microsoft Project newsgroup :)

Have you set Project/Project Information to show the Project Start Date as
1200am on 16 May? If not, I suspect it's starting at the default time of
0800 on the first day.

Thanks for the welcome Mike. I hope to learn a bit here!

I checked the project start time, it is 1200am on 16 May. I believe it
is starting at 0800 on the first day because the resource is using a
standard calendar.

The two things I would really like to understand before anything else
are why the second task ends up splitting at the end in the strange way
it does and why the second task starts at 4pm on Monday and only has one
hour of work on that day.

Using different dates makes quite a difference too; using the same
weekday on other weeks produces different results (often being exactly
what I expect in the first place).

I would really appreciate some help with either of those questions (the
first two in my original post). As is right now I am hesitant to do
much of anything with Project because it seems after studying and
working with it for a few months I can not explain things that are
happening with only two tasks and one resource involved!!

Thanks again,

David


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
MS Project MVP
See http://tinyurl.com/2xbhc for Project Tutorials



"david" <davidd31415@xxxxxxxxxx> wrote in message
news:Xns992E87E1F761davidd31415yahoocom@xxxxxxxxxxxxxxxxx
I am trying to understand certain MSP behavior which I have seen with both
2000 and 2003.

The first thing I am trying to understand is why Project splits the end of
fixed duration tasks in strange ways. Here is what I have done:

Settings:
Work starts on: Sunday
Default start time: 12:00 AM
Default end time: 12:00 AM
Hours per day: 24.00
Hours per week: 168.00
Days per month: 30

24 hr project calendar

Resource #1
Standard calendar
No availability configured

Task #1
Start date: 5/16/07
Duration: 5 days
Work: 0
Constraint date: 5/16/07
Constraint type: Start no earlier than
Predecessor(s): none
Successor(s): none
Lag: none
.

Relevant Pages

  • RE: First Time User...
    ... Duration and Work. ... Assign your resource and go to the resource usage view. ... project has the standard calendar and creates ... into the schedule for three employees. ...
    (microsoft.public.project)
  • Re: How do you assign a Resource Calendar to a task?
    ... I must be doing something wrong, because even if I create a Project file from ... scratch, create two resources (one with a Standard calendar, one based off ... then create test tasks, assining the resource with Nondefault working time, ...
    (microsoft.public.project)
  • Re: How do you assign a Resource Calendar to a task?
    ... Why don't you send me that little test file, I'll have a look and I'm sure ... scratch, create two resources (one with a Standard calendar, one based off ... assining the resource with Nondefault working ... This should show every Saturday as working time. ...
    (microsoft.public.project)
  • Are Fixed Duration tasks flawed?
    ... I believe that there is a flaw in how Microsoft Project Fixed Duration tasks ... the resource working calendar which conflict with the assignment dates, ... duration and thus forces it to behave like a FIXED Work task. ...
    (microsoft.public.project)
  • Re: Multible task
    ... Norway's Agent6 wrote: ... by 6 and then enter that many hours into each of 6 fixed duration tasks. ... that one particular resource must do in one day. ... The second scenario can be accomplished in two ways. ...
    (microsoft.public.project)