That's a solution for VBP 6.4, I have 6.2. My fault, I should have told you that detail. Still, I was able to figure it out by creating a build rule which evaluates the FAILSTEP_STATUS. When it's 1 (which means failure), skip, when its 0, build. Then it enters the next project folder which is where the FAILSTEP_STATUS is updated back to 0 to begin building that group of steps. I wrote some lines of script on the Step tab in Script Editor which sets FAILSTEP_STATUS back to 0. Here is that info.
Function vbld_StepStarting()
Set failedstatus = vbld_AllMacros()("FAILSTEP_STATUS")
failedstatus.Value = 0
End Function
Thanks for your time and help.
|