09-01-2007 12:02 AM
09-01-2007 01:11 PM
09-04-2007 09:56 AM
09-04-2007 10:18 AM
09-04-2007 12:33 PM
Actually, timing to the millisecond should be just fine. Seconds has sub-microsecond resolution.
You can access TS.ModuleTime in an expression in a subsequent step. You just need to figure out the correct elemebt to look at in Locals.ResultsList[]. Accessing the Step.LastStepResult API property is an easy way to get to the right result element, but it is not valid in an expression prior to 4.0 (you would have to use a separate ActiveX step to access that property).
One expression that will get you the result time from the immediately previous step is:
Locals.ResultList[GetNumElements(Locals.ResultList) - 2].TS.ModuleTime
The -2 is because you must subtract 1 because the array is zero-based and you must subtract another 1 because the next step adds its result placeholder to the array as soon as it begins execution.
10-06-2010 01:28 AM
Thanks James Grey,The expression help me a lot!