browse lookup phenomenon

[Kenneth Brody]

Quoting Dennis Malen (Thu, 23 Mar 2006 12:40:32 -0500):

> Ken,
>
> It does not work nor does a call statement work. Input always works.

So, if you have a processing called "foo", and you chain to it via
CHAIN "foo", the browse lookup doesn't work.  But, if you run it using
"-z foo" on the command line, it works?

> I can see the information on the first pass but I scroll up it starts to
> show me prior records. When I scroll back down to try to see the first
> record it only takes me to the record that is at the bottom of the
> screen. I can never get back to the first record unless I exit the
> processing and reexecute.
>
> Again, it was always the case for all my prior browse lookups that were
> executed by the chain statement. The people on the floor were always
> aware of it and thought that was the way it worked untill someone
> brought it to my attention and inquired why some browses worked and and
> some did not. After further investigation we confirmed that the chained
> statement was the culprit.
[...]

Given that no one else has duplicated this behavior, I still need an
explicit answer to my explicit question, which I have yet to receive
after asking several times.

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com