C
Carl Paul
We have a number of large project plans with 2000+ separate tasks. On fast
workstations Project Pro takes 5 to 7 seconds to run the calculation engine
on these projects and on slow workstations it takes 14 to 17 seconds. With
automatic calculation turned on it seems that the calculation engine is
running very, very often, and for any large project plan changes are very
slow and painful… These plans still require a lot of development so this
situation is critical.
If I turn off automatic calculation as a test, the response times become
reasonable again, and Project Pro regains its ease of use that everyone is
accustomed to.
The essential issue is whether the PMO should formally recommend that PM’s
turn off automatic calculation for these large plans. This is a real double
bind because:
The calculation engine does NOT run automatically when you save a project to
Project Server. That implies that if a PM forgets to manually run calculation
before they save, the dates in PWA will be garbage.
However, the calculation engine does run automatically when you open a
project. This means that a PM using Project Pro cannot close a project, and
then open it again to check if he/she ran the calculation engine.
The only solution that I can think of is a macro that would fire on the save
event and force a calculation. Can anyone point me to such a macro ?…. Or
have another good solution?
workstations Project Pro takes 5 to 7 seconds to run the calculation engine
on these projects and on slow workstations it takes 14 to 17 seconds. With
automatic calculation turned on it seems that the calculation engine is
running very, very often, and for any large project plan changes are very
slow and painful… These plans still require a lot of development so this
situation is critical.
If I turn off automatic calculation as a test, the response times become
reasonable again, and Project Pro regains its ease of use that everyone is
accustomed to.
The essential issue is whether the PMO should formally recommend that PM’s
turn off automatic calculation for these large plans. This is a real double
bind because:
The calculation engine does NOT run automatically when you save a project to
Project Server. That implies that if a PM forgets to manually run calculation
before they save, the dates in PWA will be garbage.
However, the calculation engine does run automatically when you open a
project. This means that a PM using Project Pro cannot close a project, and
then open it again to check if he/she ran the calculation engine.
The only solution that I can think of is a macro that would fire on the save
event and force a calculation. Can anyone point me to such a macro ?…. Or
have another good solution?