I'm a power user of Microsoft Project. We work programs with 10's of 1,000's of activities in an Integrated Master Schedule. We use Microsoft Project for most of these programs because that's what the government customer wants us to use. They use Project because it's cheap, works OK, and is easy to use.
Microsoft Project is one of those tools build for one purpose and has evolved to other purposes. It is not used inside of MSFT in the way we use it. If it was they completely bone headed features we encounter every day would have been fixed years ago.
Here's the latest.
A client has 2010 I don't. He sent me a file. I can't open it. No problem, I'll install the convertor. STOP. The 2010 run time environment for VBA is different than the 2007 environment and many of our macros get clobbered. By many I mean 10's of 1,000's of lines of VBA that connect our 2007 instances to ERP systems, Earned Value Engines and other instances of MSFT Project.
If MSFT actually used Project to run their business in the way we use it to manage billions of dollars of defense and space work, they'd fix this crap. This is why any respectable construction firm uses Primevera.
Hey MSFT start eating you're own dog food, just like Larry Ellison does.
