R
Robert
I'm looking for opinions here. In general do people find it easier to use master project files to consolidate numerous "sub-projects" or to simply create huge project files with numerous phases and summary tasks. Our company is working on several (over a dozen) projects throughout the year that are all centered around the same goal (from different angles). Having never used project before, I went at it by constructing one monstrous file that contained each project shown as summaries of the whole. Now that I've been working with Project for awhile and I've read up on it a bit, I think the master file/individual projects approach would work better when coupled with a resource pool.
I know I'm giving you a very vague scenario here, but anyone have any opinions? The current file is large (17mgs), takes awhile for calculations, and likes to corrupt itself. I figure if I was working with lots of individual files working out the bugs would be much easier. Are there any major drawbacks to this approach?
-Robert
I know I'm giving you a very vague scenario here, but anyone have any opinions? The current file is large (17mgs), takes awhile for calculations, and likes to corrupt itself. I figure if I was working with lots of individual files working out the bugs would be much easier. Are there any major drawbacks to this approach?
-Robert