![\"\"](\"http:\/\/changeinspector.com\/blog\/wp-content\/uploads\/2012\/10\/setdefaultproject.bmp\" "\\"setdefaultproject\\"")
<\/a><\/p>\nSet Default Project Dialog Box<\/p>\n
<\/p>\n
Another issue with working with multiple schedules arises if these schedules have different data dates.\u00a0 Each project will be scheduled based on its own Data Date.\u00a0 The earliest data date of all open projects will be shown as the data date on the Gantt chart. The data dates for individual projects can be changed when applying actual dates but not when scheduling.<\/p>\n
New to P6, Service Pack 2 (P6.2) is the option to calculate the total float based on the finish date of each project in a collection of schedules or on all opened schedules.\u00a0 Previously, when a project containing multiple schedules was opened, P6 calculated the dates based upon the early finish of the last activity in each schedule.\u00a0 This meant each schedule calculated the critical path independently, even if they were tied together in a network of relationships.\u00a0 The older method fails to identify the single critical path for a project of multiple schedules.\u00a0 The down-side of the new option is, other than viewing the scheduling log, there is no indication as to which option was used when later reviewing the results of a CPM computation. On the other hand the Longest Path still only works on one schedule at a time \u2013 you cannot produce a multi-schedule longest path.<\/p>\n
P6 provides 3 different types of access modes when opening a project, Exclusive, Shared and Read Only shown below.\u00a0 If the project is opened in shared mode, then multiple users can modify or update the schedule simultaneously. \u00a0This results in confusion and it is strongly recommended schedules are opened in Non-Shared access modes.\u00a0 If the schedule is opened in Shared mode then F5 key must be pressed regularly to refresh the schedule otherwise one person can overwrite another\u2019s changes.<\/p>\n
<\/p>\n
Project Access Mode<\/p>\n <\/p>\n If external relationships are used between projects and if these projects are replaced by importing a new update or a new version of the schedule then the relationships are not automatically recreated.<\/p>\n Another issue with the external relationships is the relationships are lost if only a single project is exported.\u00a0 In cases like these where the external relationships are lost, P6 attempts to maintain the proper timing by internally constraining the appropriate early\/late dates of the activities missing their inter-project relationships.\u00a0 This causes the schedule to mimic the effects of the relationship at the time of the export.\u00a0 The imposed constraints will not show up under the task\u2019s constraint boxes, as these are internally imposed.\u00a0 The only indication of an imposed constraint will be an asterisk printed to the right of the date in the Start or Finish column.\u00a0 These constraint dates will only be visible in the External Dates columns, if displayed.\u00a0 To force P6 to ignore such external constraints, the scheduling options tab has a setting for -\u201dIgnore relationships to and from other projects\u201d. This can also fix extreme negative float values.\u00a0 You can also remove the external constraints entirely from your schedule by showing the External Early Start and External Late Finish columns; remove the external dates shown, and then recalculate the schedule.<\/p>\n","protected":false},"excerpt":{"rendered":" One of the big strengths of P6 is its ability to group any number of schedules into a Master Schedule simply by putting the schedules into an EPS.\u00a0 Opening EPS will open all of the otherwise independent schedules, even if … Continue reading <\/a><\/p>\n