// "In "general use," one can't reliably presume a correlation between the ID sequence and the logical sequence." //
Understood. In this case it's a factory production schedule that by fiat gets used in a particular format over and over so I have pretty tight control on how it's sorted.
In "general use," one can't reliably presume a correlation between the ID sequence and the logical sequence. Still, as you've explained, this certainly seems to offer a bit of streamlining for that particular (ZFF) issue.
Rgds, t
Member for
7 years 1 month
Member for7 years1 month
Submitted by ThinAirDesigns on Thu, 2019-05-02 23:14
As to its usage, I actually just successfully used it to modify your ZFFImpose function. I've been creating schedules with tasks such that I needed to loop through multiple times to get all the float out of all the faux-ZFF relationships (programatically constraining one task simply moved the float up to the previous task requiring another run through).
My previous schedule had a known number of these relationship layers (3) so I just looped through your code three times. Now I have a schedule that the users might add an unknown number and I needed a more elegant solution than my previous clutz.
Going through backwards allows your code to now remove the float as far up the chain as needed in one go-round.
I'm a programming hack, so you might have come up with a cleaner solution, but this works slick as a whistle as written.
Member for
6 years 2 monthsThanks Tom for the code!
Thanks Tom for the code!
Member for
7 years 1 month// "In "general use," one
// "In "general use," one can't reliably presume a correlation between the ID sequence and the logical sequence." //
Understood. In this case it's a factory production schedule that by fiat gets used in a particular format over and over so I have pretty tight control on how it's sorted.
Thanks again.
JB
Member for
18 years 11 monthsJohn,Glad you got it
John,
Glad you got it sorted.
In "general use," one can't reliably presume a correlation between the ID sequence and the logical sequence. Still, as you've explained, this certainly seems to offer a bit of streamlining for that particular (ZFF) issue.
Rgds, t
Member for
7 years 1 monthThat's it Tom ...
That's it Tom ... THANKS.
The task.count property was the secret and this link didn't list it for whatever reason:
https://docs.microsoft.com/en-us/office/vba/api/project.task
As to its usage, I actually just successfully used it to modify your ZFFImpose function. I've been creating schedules with tasks such that I needed to loop through multiple times to get all the float out of all the faux-ZFF relationships (programatically constraining one task simply moved the float up to the previous task requiring another run through).
My previous schedule had a known number of these relationship layers (3) so I just looped through your code three times. Now I have a schedule that the users might add an unknown number and I needed a more elegant solution than my previous clutz.
Going through backwards allows your code to now remove the float as far up the chain as needed in one go-round.
I'm a programming hack, so you might have come up with a cleaner solution, but this works slick as a whistle as written.
THANKS (for both the original code AND the mod)
JB
Member for
18 years 11 monthsHi John, this will do what
Hi John, this will do what you ask, though I can think of no good general-use case. Good luck, tom
Dim t As Task
Dim i As Long
For i = ActiveProject.Tasks.Count To 1 Step -1
Set t = ActiveProject.Tasks(i)
If Not t Is Nothing Then
'Your Code Here
End If
Next i
End Sub
Member for
18 years 11 months[Delete duplicate]
[Delete duplicate]