There are several approaches to this concern.
A) Do two actions in one active link. Change Field --> refresh table Set Field --> stuff $LASTCOUNT$ into a temp field. Or... B) Do two active links separated by one execution order: AL1 : Execution order 10 Change Field --> refresh table AL2 : Execution order 11 Run IF: Test based on $LASTCOUNT$ OR Set Field --> stuff $LASTCOUNT$ into a temp field. Or... (for the real paranoid) C) Use an Active Link guide to make sure no one accidentally slips in another active link at the second execution order or mucks with the temp field value. (Can be used in combination with either of the above design patterns.) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 12/20/06, Mike White <[EMAIL PROTECTED]> wrote: <snip>
It seems to me that $LASTCOUNT$ could be risky; other workflow could execute a search, disturbing your count from a TF refresh before you test it. Manageable, but you'd need to be extra careful. Mike White Office: 813-978-2192 E-mail: [EMAIL PROTECTED]
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
