when field processing

[GCC Consulting]

> John Esak wrote:
> [...]
> > Yes, of course, sorry, but I should have gone on to explain what 
> > carries on even after that... once you've pressed U and then 
> > eventually ESCAPE/ESCAPE, the INPUT table runs and then the 
> auto table 
> > runs a third time and then the @entsel runs its second 
> time. So, what 
> > I meant to say was... when retrieving an and updating an existing 
> > record in clerk, the auto table runs three times, input as 
> many times 
> > as control is passed back and forth between the user and the 
> > processing table, and @entsel runs twice. Now, that's 
> completely clear 
> > as mud. :-)
> 
> Yes, assuming you are not in a mode that goes to another 
> record (such as "add records" mode), after saving the record, 
> filePro will once again run automatic processing on it before 
> going back to the "enter selection"
> prompt and @ENTSEL.

So, may we assume that if the is processing that is at the top of the table
starting at line one that needs to run after the record is saved and @update or
@entsel was used to access the record, there should be a GOTO or GOSUB top(label
at line 1?   

I will assume that the @update or @entsel will run from the first line of the
routine.  Therefore a flag will need to be set to execute the GOTO top or GOSUB
top?

Richard Kreiss