Browse Lookup

[Rodgers Hemer]

On Jul 28, 2008, at 3:49 PM, Kenneth Brody wrote:

> Quoting Rodgers Hemer (Mon, 28 Jul 2008 15:42:02 -0700):
>
>>
>> On Jul 28, 2008, at 3:27 PM, Kenneth Brody wrote:
>>
>>> Quoting Rodgers Hemer (Mon, 28 Jul 2008 15:19:37 -0700):
>>>
>>>> SCO 6.0    filePro 5.0.14
>>>>
>>>> I am using a browse lookup in a header file to select records in a
>>>> detail file for editing.  Thirteen records appear on the browse  
>>>> screen
>>>> but the total records in the lookup could be several hundred.
>>>> Subsequent to saving the detail record, @BR is used to calculate  
>>>> the
>>>> number of pushkeys to move the selection highlight to the next  
>>>> record
>>>> in the browse window.  This works well until the user goes beyond  
>>>> the
>>>> thirteenth record as @BR will not go beyond the maximum lines in  
>>>> the
>>>> window.  So the highlighted record is a function of 13 and is  
>>>> within
>>>> the first 13 records in the browse.
>>>>
>>>> Does anyone have a suggestion on how to force the cursor highlight
>>>> beyond the first 13 records?
>>>
>>> Sounds like a job for "show=pkeep".
>>>
>> Ken:
>>
>> I am using show=pkeep.  The applicable parts of the lookup  
>> statement are:
>>
>>     lookup ipd = pslipd@  k=1  i=A  -npxm  b="(brw=17,4,-1 show=pkeep
>> fill=asc,top)"
>
> Then, unless you are doing something to take the browse window down,  
> the
> cursor would remain where the user left it, and there's no need to  
> do a
> PUSHKEY to move the cursor back to the same spot.
>
> If you need to take the window down for some reason (which would  
> negate
> the functionality of the pkeep), then you could add an additional  
> key to
> the index to make each record unique, and then lookup to that unique  
> key.

Ken:

I removed the pushkey processing and the the cursor always returns to  
the first browse record.  The window is not taken down but I am using  
getnext to get the next record in the browse.  Would that be causing  
the problem?

Rodgers Hemer