• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Question on MS Project

D

DJFuji

Diamond Member
I've got about 6 projects i'm heading up at work that i want to document in MS project. I'm writing up the tasks and am wondering if its better to create separate project files for each actual project or use the cascading aspects of tasks to put each project in one file as a task and have their associated tasks as subtasks? This means i can view my entire workload in one file but i'm not sure if that will cause problems later. Comments?
 
I have always believed in keeping each project seperate.

Mainly because I had to provide the info to different people that had o knowledge/cares of other projects being worked on or supported.

Also, a couple were for independent clients.

You may be able to create a master project and link in the indivigual projects.
It make sense to be able to, whether it can be done is another story.
 
Thanks eaglekeeper. I guess i'll give it a try and see what works best for me. The only bad thing is not being able to have a wide overview of all my projects. I'll have to look at each one individually.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top