Duration is always the time from when a task begins until it's done. With
multiple resources, it's from whenever the earliest starting resoiurce
starts until the latest finishing resource finishes, regardless of whether
they work together or independently. If I have a task that has 2 days of
work split between Joe and Bill, Joe does his work on 01 April and Bill does
his on 01 May, the duration of the task will be 4 weeks. If they both work
together, the duration will be 1 day. If Joe does his on Mon and Bill does
his on Tue, the duration will be 2 days. Same 2 man-days of work, same 100%
resource assignment for both in all three cases.
Your initial post could be explained in a couple of ways depending on how
you're assigning resources. First of all, the difference between effort
driven and non-effort driven only kicks in when you add or remove resources
AFTER the INITIAL resource assignment. Whether I put on one guy or 20,
whther they're assigned 100% or 10%, duration never changes with the initial
resource assignment. It is as if Project was saying to itself "When he
estimated that the task would take XX days, he knew that this was the
resource assignment he was going to use and that formed the basis of his
estimate" and it doesn't mess around with it. It's only when you change you
mind and alter the resource assignment later that it looks at the effort
driven setting to decide how to handle the change. So the first question to
ask you is, are you assigning the resources one after the other or are you
assigning them all at once?