Using risk+ with Project 2007

[Renee H]

Has anyone experienced issues with running Risk+ and project 2007? It seems
to work for us but is extremely slow.

 

[Jim Aksel]

We use Risk+ and Pertmaster Risk Expert on both P2003 and P2007. No
significant change in performance on Risk+ in either version of desktop MSP.
Typical schedules include Master/Subprojects. Compared to Pertmaster, Risk+
runs quite slow in all insntances. We did see a marked improvement with
Pertmaster moving from P2003 to P2007 .... P2007/Pertmaster is the fastest
combination we've used. If you need additional input, post back.
--
If this post was helpful, please consider rating it.

Jim

Visit http://project.mvps.org/ for FAQs and more information
about Microsoft Project

 

[gugliupj]

I just finished running both Risk+ & Pertmaster. Both seem to take
significantly longer with 2007 they did with 2003. I have a Project file
with about 1600 lines in it and it takes 40 mins to run 1000 iterations in
2007. With 2003 it took 20 minutes on a bad day.

Pertmaster did run the risk analysis faster but it took 1.5 hrs to import
the project file. It used to take 50-55 mins.

The other thing I noticed is that simple macros that took 5 mins to run in
2003 are taking almost 30 mins to run in 2007.

I know this isn't a solution but I didn't want you to think you were going
crazy.

 

[Rod Gill]

Hi,

A 5 minute macro taking 30 minutes suggests something is wrong. With 2007
(due to needing more memory) I would expect it to be slower, but no more
than 20-50% and certainly not 600%!

--

Rod Gill
Microsoft MVP for Project - http://www.project-systems.co.nz

Author of the only book on Project VBA, see: http://www.projectvbabook.com

I just finished running both Risk+ & Pertmaster. Both seem to take
significantly longer with 2007 they did with 2003. I have a Project file
with about 1600 lines in it and it takes 40 mins to run 1000 iterations in
2007. With 2003 it took 20 minutes on a bad day.

Pertmaster did run the risk analysis faster but it took 1.5 hrs to import
the project file. It used to take 50-55 mins.

The other thing I noticed is that simple macros that took 5 mins to run in
2003 are taking almost 30 mins to run in 2007.

I know this isn't a solution but I didn't want you to think you were going
crazy.



__________ Information from ESET Smart Security, version of virus
signature database 4875 (20100217) __________

The message was checked by ESET Smart Security.

http://www.eset.com

__________ Information from ESET Smart Security, version of virus signature database 4875 (20100217) __________

The message was checked by ESET Smart Security.

http://www.eset.com

 

[gugliupj]

Is there a setting I can fix in 2007?

Hi,

A 5 minute macro taking 30 minutes suggests something is wrong. With 2007
(due to needing more memory) I would expect it to be slower, but no more
than 20-50% and certainly not 600%!

--

Rod Gill
Microsoft MVP for Project - http://www.project-systems.co.nz

Author of the only book on Project VBA, see: http://www.projectvbabook.com






__________ Information from ESET Smart Security, version of virus signature database 4875 (20100217) __________

The message was checked by ESET Smart Security.

http://www.eset.com



.

 

[Rob Schneider]

Suggestions:
1. that you have the latest service pack
2. that Windows is up to date
3. your computer memory is working ok (and you have enough)
4. consult with the vendor of risk+

there is no setting in Project to "speed it up". It's up to the
computer, frankly.


--rms

www.rmschneider.com

 

[Rstamp12]

With 2007, it is significantly slower in most cases and there are a few
things you need to do. turn off any formulas, get rid of any "Must" type
constraints. you can turn off the shade change highlight under views and
copy the file to your desktop vs. a server. I'm finding it extremely painful
to get it to run in any normal timeframe and Deltek doesn't know what to tell
you either. MS added something or things to 2007 which are running in the
back ground.

Good luck.