One possible workaround for your immediate problem would be to replace all lags with dummy tasks. You may then control the calendar of the dummy tasks.
It is indeed true; MS Project uses the project default calendar for lags. P3 uses the predecessor activitys calendar, and P3ec uses any calendar it wants to. Good luck!
There is a long discussion on the subject (albeit at a more general level) where it is easy to see that different scheduling packages handle multiple calendars and calendars for lag relationships very differently:
I really did not wish to disclose which systems I was using, but since you have a direct question and a specific need, I will share that in my testing, it appeared that MS Project was indeed using the default project calendar for the lag relationships irrespective of the calendars for the predecessor or successor tasks. I did not attempt to import an existing schedule into another schedule using a different default calendar, but it would appear from your post that doing so does not change the calendar for the lag activities.
You might try exporting the most basic data possible and re-importing. Perhaps you can find a medium that does not communicate the calendars for relationships.
RE: Effect of Calendars on Task Links
One possible workaround for your immediate problem would be to replace all lags with dummy tasks. You may then control the calendar of the dummy tasks.
Bernard Ertl
eTaskMaker Project Planning Software
RE: Effect of Calendars on Task Links
It is indeed true; MS Project uses the project default calendar for lags. P3 uses the predecessor activitys calendar, and P3ec uses any calendar it wants to. Good luck!
RE: Effect of Calendars on Task Links
There is a long discussion on the subject (albeit at a more general level) where it is easy to see that different scheduling packages handle multiple calendars and calendars for lag relationships very differently:
What do you expect?
I really did not wish to disclose which systems I was using, but since you have a direct question and a specific need, I will share that in my testing, it appeared that MS Project was indeed using the default project calendar for the lag relationships irrespective of the calendars for the predecessor or successor tasks. I did not attempt to import an existing schedule into another schedule using a different default calendar, but it would appear from your post that doing so does not change the calendar for the lag activities.
You might try exporting the most basic data possible and re-importing. Perhaps you can find a medium that does not communicate the calendars for relationships.
Bernard Ertl
eTaskMaker Project Planning Software