chain from @wlf
Nancy Palmquist
nlp at vss3.com
Fri Apr 15 12:17:41 PDT 2005
Joe Chasan wrote:
> fp 5.0.14, unix.
>
> Is anyone using chain command successfully from @wlf while within
> update on a record within *clerk?
>
> I have a table that works by itself, works when chain'ed from @key,
> yet if i chain to it from within update on a record from @wlf, within
> the chain'ed to table clerk is completely confused as to what line #'s
> it should be executing, going to lines that are never referenced,
> executing partial subroutines, or giving SegV's.
CHAIN starts a replacement process table. I have never seen it work
from a WHEN of any kind. I would use CALL for that.
I do use it when I need full input processing control or need to change
the output table run based on record logic. (A generic form that can be
loaded based on the record data using different process tables to do
different form layouts.) You can not change the name of the output but
designed correctly, it can look like an entirely different output based
on the data. I don't just mean different fields are filled in with
different data, I mean the headings, layout, everything.
Back to CHAIN. When I end a CHAIN, it does not return it actually ends
the processing just like an end in the INPUT table would do. To go back
you much do a CHAIN "input". That will cause the input table to start
at the beginning. It is not a return to the point of the original CHAIN.
Nancy
--
Nancy Palmquist MOS & filePro Training Available
Virtual Software Systems Web Based Training and Consulting
PHONE: (412) 835-9417 Web site: http://www.vss3.com
More information about the Filepro-list
mailing list