similar to the other line of dots...

[DougSain]

My question is a bit more problematical.

An example first....

I have a task that is set to 2 days (estimated) duration.

I have some VB6 add-in code running that responds to resources being added. If the resource is "half an expert" the duration is set to 4 days.

The problem is when I set the duration to 4 days, its gets auto-set to 0. On the next line I catch that and just set it again....then I get a 4 day dotted line and then a 4 day task box....

So:

In ProjectAssignmentNew(..)

CurrentTask = (task this assignment is for)
Resource= resource from the new assignment

If Resource is half an expert
CurrentTask.Duration = 4days
(this , for some reason, results in setting the duration to 0... )
IF currentTask.duration = 0, then set to 4 days again
(now the duration is right, but the gantt chart is messed up)

If Resource is twice an expert
CurrentTask.Duration = 1 day
(works fine)

Any thoughts?

 

[Jan De Messemaeker]

Hi Doug,

This is what happens when work on the task is 0 or in other words the
resource is assigned with 0% units.
Change that and your dots will melt away.
HTH

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/index.htm
32-495-300 620

My question is a bit more problematical.

An example first....

I have a task that is set to 2 days (estimated) duration.

I have some VB6 add-in code running that responds to resources being

added. If the resource is "half an expert" the duration is set to 4 days.

The problem is when I set the duration to 4 days, its gets auto-set to 0.

On the next line I catch that and just set it again....then I get a 4 day
dotted line and then a 4 day task box....

 

[Jan De Messemaeker]

Hi Doug,

Nothing in my versions. For some reason the drop-down method generates a 0%
assignment .
HTH

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/index.htm
32-495-300 620

Hey,

Thanks for the info....

Another quirk I noticed.... this problem only arises when you add a

resource from the "Resource Names" drop down in a Task View.

If you double click a Task, and add resources using the Resource tab,

everything works fine (even if you assign just one Resource).