browse lookup phenomenon

[Dennis Malen]

Ken,

It does not work nor does a call statement work. Input always 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.

Dennis
----- Original Message ----- 
From: "Kenneth Brody" <kenbrody at bestweb.net>
To: "Dennis Malen" <dmalen at malen.com>
Cc: <filepro-list at lists.celestial.com>
Sent: Thursday, March 23, 2006 11:12 AM
Subject: Re: browse lookup phenomenon


> Quoting Dennis Malen (Wed, 22 Mar 2006 18:47:27 -0500):
>
>> Ken,
>>
>> I tried the -z and created a call processing. They both did not work
>> properly. The only thing that worked as it should was "input" (@key).
> [...]
>
> I don't understand what you mean.
>
> If you take the processing that you chain to (where you say it doesn't
> work) and, rather than chaining to it, simply use it directly as the
> input processing with the "-z" flag, does it work there?
>
> --
> KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
> http://www.hvcomputer.com
> http://www.fileProPlus.com
>
>
>