Because MS Project yields wrong float calculations after resource leveling it might be impossible to create a macro to set free slack to zero under resource leveling using the computed values of float.

In the following example after the resource leveling is run MS Project yields wrong float values and by setting wrong float values to zero the schedule is delayed and becomes unleveled, then in order to level it you must run again the resource leveling and then after setting your wrong values of float equal to zero you end up delaying once more time the whole schedule. MS Project ridiculous float computations might yield ridiculous results.

http://www.youtube.com/watch?v=ciTfD1Tgw9E

Is common sense, MS Project calculations for float under resource leveling are wrong therefore any attempt to set zero float after resource leveling using wrong float values will yield wrong results.

As Lady Gigo sings, Garbage In - Garbage Out

Primavera SureTrak same as MS Project yields wrong float values after resource leveling but they have a zero free float constraint with their option for ALAP. Therefor it is not impossible to get to it, surely not by means of their float computation.

But beware that SureTrak wrong computations of float after resource leveling yields weird implementation of the Zero Free Float constraint, is kind of unpredictable same as P3.

http://www.youtube.com/watch?v=AQPaM5Vxvpw

Why do you think early users of P3 could not figure out the logic in their schedules if from the very beginning float values were wrong?

I would not be surprised at all if latest versions of Pertmaster still display wrong values of float after resource leveling.

Andrew,

You could probably use the ProjDateDiff-function which takes the calendar of your choice into consideration. Date1=Early Start, Date2=Early Start+Free Slack, calendar="your calendar" (from MSP Help: ...the calendar to use when calculating the duration. If calendar is not specified, the default for the current resource is the resource calendar, or for the current task, the task calendar (or the standard calendar if there is no task calendar)).

Otherwise I can suggest to post your question on: http://social.technet.microsoft.com/Forums/en-US/projectprofessional2010general/threads where some people with really good knowledge of macros and VBA within MS Project are normally very helpful to answer your questions. Probably the biggest forum for discussion of MS Project. Free, but requires a Windows Live ID.

Regards,

Bo

Andrew,

I agree with you don't give up yet.

Please take a look at the following formula and then the following screen movie that might give you some hints.

http://www.youtube.com/watch?v=U9xaQHOXXXI

You can make your Paste Special to be applied to the whole column/all activities or to individual activities.

For the undo macro you might need to temporarily copy-paste Date 1 into constraint date without special paste, then you will be able to remove the constraint.

Best regards,

Rafael

P.S. - GIGO

For years people have been asking for Microsoft to provide Zero Free Float Constraint instead of their implementation of Zero Total Float Constraint for ALAP (as late as possible).

Remember such macro shall be applied to individual activities because if applied to all it will have the same effect of the Zero Total Float Constraint.

Wish you good luck in your search for such macro. In theory a simple computation.

Free Float (FF) = ES of next earliest successor - EF of activity

I believe both are useful, unfortunately it is not what you need but what the software gives you. The software developer will tell you they know how to plan and you do not. That if you do not do it their way then you are wrong as they are the owners of absolute truth and that for your good they will not implement such functionality.

At times I miss SureTrak a low cost software that provided for both constraint options plus the expected finish constraint useful for long lead procurement activities. Also miss the WBS Activity Type and the Topic Activity Type. There is no such thing as a software with all the bells and wissels and we must learn to live with such reality.