Forum Sponsor:

Viewer for .xer, xml and xls schedule files Schedule Reader™Free Trial

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Float using Mandatory = 30 dy float for example, but "On or Before" same dates sais 0 - why? should be 30 also...

1 reply [Last post]
John Reeves
User offline. Last seen 5 weeks 1 day ago. Offline
Joined: 10 May 2013
Posts: 46
Groups: None
Is there a setting that handles this...? Float using Mandatory = 30 for example, but if using "On or before" exact same date sais 0 instead of the 30 days - why? should be 30 also...I used P3 longer than P6 but if I add a finish on or before Constraint for 30 days after the showing completion date shouldn't that give me 30 days float?  (I know it would in p3)  I don't like using the mandatory date and have generally read that using the Project "Must Finish By" constraint in never a good idea - even though it fixes this least my interpretation of Ron Winter SA software... - this is on P6 Ver 8.3 P6E version - if feel a setting perhaps was changed...


Zoltan Palffy
User offline. Last seen 34 min 8 sec ago. Offline
Joined: 13 Jul 2009
Posts: 2531
Groups: None

never ever evr use mandatory anything becsue it means just that. I think you have this reversed mandatorty will always say 0 and on or before will give you the corect float value.

This is becasue if the date calculated is ON or BFORE the constraint date the float wil be positive. If the date calculated is after the ON or BEFORE constraint date then the float will be negative.

There are 2 wasy to handle the completion date of a project. You can put a finish on or before constraint date on your last activity and or put a project musft finish by date on the project itself. 

If you do not use a project must finish by date and if you happen have a activity without successor then the late dates will be equal to the early dates and the float value will be incorrect. If you use a project must finish by date and are missing a successor the backward pass will start from the project must finish by constraint date and work backwards. 

I perfer use the project must finish by date so the backward pass knows where to begin and the float valure are correct. 

If you do not have a project must finish by date or a finish on or before constraint date on your last activity then there is no place to start the backward pass and you float will ALWASY be 0