Tagged: master schedule
- 02/27/2019 at 8:01 pm #415003
I need to create a master schedule in Project 2016 Standard with upto 20 embedded subprojects that have been created using a variety of Standalone Client MS Project versions i.e. 2007, 2010, 2013 and 2016. i.e. I am not linking them.
I was going to create a standard template for use by the master and subprojects so that common information can be reported / rolled up. Will a template need to be created using each version of project or just do once in 2016?
Is this possible or are there technical or other reasons why all embedded files should be created using the same version of project.
I’m assuming that I would need to ensure calendars, customised fields, project start dates are all standardised. Anything else I would need to be aware of?
Many thanks for your help.
Emma02/27/2019 at 11:09 pm #415004
Emma, I’ve done what u propose with files going back to 2010, and any major issues were cosmetic – where older files that are customized by the owners (currencies, columns, colors on the gantt, fonts, etc.) would display in unexpected ways when opened within the master (i.e. expanded out). If your files are standard project files (no customized formulas to fields or inserted VBA), u should be fine, but I think the only way to know for sure is to fire up 2016, insert the files one at a time, and check for functionality & integrity. But theoretically, what you want to do is possible. Best, Jigs02/28/2019 at 9:28 am #415005
Hi Emma. I am with Jigs that I have not found any issues myself with combining different versions, but I’ll admit that I haven’t done that very much. I have heard though, that the practice is not recommended. I heard others state emphatically that doing this will eventually cause corruption.
With that said I would be careful mixing and matching four different versions. That I haven’t seen before and would probably stay away, especially if the master project is updating its corresponding sub-projects of various versions.
So I agree that “theoretically” that will work, but you’ll find recommendations on both sides of the issue.02/28/2019 at 1:58 pm #415006
Thankyou. Jigs when you say no customised formulae, I was planning to use formulae within customised fields to create exception flags. What is the issue with these?
Would either of you have suggestions for doing this another way? The only thing I could think of was not ceating a master schedule and instead using export maps to put the sub project data into excel and then reimport or copy it into a single 2016 file?02/28/2019 at 3:33 pm #415007
A couple of general thoughts based on what others have stated/experienced. 1. don’t update sub-projects when you are working through the master project. 2. update specific project schedules using the same version. Normally I’m with Jigs and am not that worried, but I’ve never seen anyone work through four version simultaneously. Better safe than sorry. Hope this helps…02/28/2019 at 9:39 pm #415008
@Emma, I was referring to custom fields /formulas / VBA / etc. written back in 2007 that may have worked then, but may now work now due to changes over the years. I doubt u would have any problems writing / inserting fresh ones.
I’ve had to do just what you propose in a classroom setting, where each student would have files produced from different versions of MSP (there must have been some 2007 files in the mix back in the day), and I would always have the latest up on the lectern.When we got to the lesson on Master Plans, I would solicit project files from the students and throw a master together from that (always fun to do). Occasionally something would not look right or I’d get an error, but I would just use another file and quickly move on, never bothering to troubleshoot during class. After class, it was often found that the broken file had come from 2010, or came from an infected Windows platform (at which point I would stop touching that machine and sanitize my hands).
BUT, since you have the files in a controlled environment, you could just open them and save them using 2016, making sure they work independently. If they work independently (everything calculates correctly), they should work as subs in a master plan. I would not export the data from a file unless it was clearly messed up and hopeless, and I certainly would not mash all the exports together into a new file, unless that was my last resort. Best of luck, Jigs