May 13, 2016 10:20 AM
Replying to Linda Zinn
...
2007 was awful. We did a beta test on it and decided to scrap the idea and stay with a single master schedule on a server. 2010 was night and day. We implemented that about two years ago and them migrated to 2013 last summer. I like 2010 better than 2013. The made the "excel" like datasheet list view web based and it is clunky as all get out.
That being said, so far the sub-project feature is pretty slick. The only downsides I see so far is you can only add predecessors and successors to the highest level summary tasks (usually the project name) and the subsite on the sharepoint side leaves a lot to be desired. All you really get there is a common URL naming convention and if you drill down into site contents you can see you have one.