Browse Lookup Selections

[Rodgers Hemer]

On Jul 2, 2008, at 10:55 AM, GCC Consulting wrote:

>
>
>> -----Original Message-----
>> From: filepro-list-bounces+gccconsulting=comcast.net at lists.celestial.com
>>
> [mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.celestial.com 
> ]
> On
>> Behalf Of Bruce Easton
>> Sent: Wednesday, July 02, 2008 1:28 PM
>> To: filepro list
>> Subject: RE: Browse Lookup Selections
>>
>> Rodgers Hemer wrote Wednesday, July 02, 2008 12:55 PM:
>>> SCO 6.0, FP 5.0.14
>>>
>>> When using a browse lookup from a header file to a detail file (that
>>> may have from 1 to 999 records), I want to move the selection cursor
>>> in the lookup selection window to the line following the line that  
>>> had
>>> been previously been selected and viewed.  I use a getnext command  
>>> to
>>> put the user back into the browse selection window after hitting  
>>> ESC-
>>> ESC when modifying the previously selected detail record.  I have
>>> tried looping through a pushkey command for CDWN based on the line
>>> number of the previous selection before the getnext but that doesn't
>>> seem to work.  Perhaps I have the pushkey command at the wrong place
>>> in the input table.  I do not know of any other command that will do
>>> what I want.
>>>
>>> Does anyone have a suggestion that would make the pushkey command
>>> work, or is there another command that would highlight the proper  
>>> line
>>> in the browse window?
>>>
>>> Thanks in advance for any ideas.
>>>
>>> Rodgers Hemer
>>
>> If, for the browse line record that you allow the user to view (a  
>> popup,
>> perhaps?)
>> and its associated functionality, you do not need to take down the  
>> browse
>> before re-execution, then you should be able to use a combination of
>> SHOW=PKEEP for the browse along with a conditional PUSHKEY "[CDWN]"
>> just before the browse line is executed.
>>
>> If you do take the browse down before re-execution (to provide some
>> multi-layer
>> functionality), then I think you do need to use pushkey to do the  
>> whole
> job
>> - and it is doable - you can build a separate lookup routine (using  
>> the
>> same
>> index that you use in the browse lookup) with factors: parent key,
>> # lines showing in the browse, rec# of last viewed record (capture  
>> this
>> before showing a detail record) to generate the proper string to push
>> (i.e., "[DTAB][DTAB][CDWN][CDWN][CDWN]").
>>
>> Bruce
>>
>>
>> Bruce Easton
>> STN, Inc. - Authors of the filePro Developer's Reference
>
> One can capture the cursor location in the browse using @br - row in  
> browse
> window.  If you close the window, set something like br(2,.0)=@br.   
> You then
> can use that information to calculate your pushkey.  Just keep in  
> mind that
> this is the row in the browse window starting at the top and not the  
> line #
> of the cursor position in the window.
>
> Richard Kreiss
>
Richard:

I appreciate your suggestion to use @br which I hadn't remembered was  
available.

Bruce:

I was doing what you suggested but had neglected to reinitialize one  
dummy field each time.  Your comments made me go back again and debug  
the process.  Works great now and the customer is delighted.

Rodgers Hemer
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list