Browse Lookups

[Richard Kreiss]

I did this years ago be counting the records to appear in the lookup or report and the dividing by the length of the scroll bar. That let me know how many records had to be processed before setting a 1 character field’s value to a graphic character for display. Ds=ds{ds when the execution value was met. You can even put up % complete values or display that value as a show. 

With a browse, you will need to set this as a subroutine to be run along with Any other processing. Keep in mind that once all the records are selected in a browse, moving through the records will cause the scroll routine to run again. You will need to block any key strokes that cause the browse to execute this sub routine. 

For Windows based computers, I have not seen the issue of a browse appearing to be frozen. This was an issue in the early ‘90’s. 

As for the report output, this was done for a client’s bookkeeper so that she could glance at a screen and have a visual idea of how far along the report generation was. Again, the speed of today’s machines has made this unnecessary. 

Richard
Sent from my iPhone

> On Jun 25, 2018, at 3:40 PM, Walter Vaughan Jr via Filepro-list <filepro-list at lists.celestial.com> wrote:
> 
> I had sort of the same Idea that one could show boxes/lines incrementing across the bottom of the screen  like  the illusion of a progress bar, however I'm curious how one would trap  knowing that you are not locked up. How would you know in the "prc= " code that you had gotten to the end and need to take it down? Typically after the browse I've only  checked for @bk keys. So one could change the show box status to "Completed" before checking for @bk's?
> 
> 
> 
> -----Original Message-----
> From: Filepro-list [mailto:filepro-list-bounces+wvaughan=steelerubber.com at lists.celestial.com] On Behalf Of Fairlight via Filepro-list
> Sent: Monday, June 25, 2018 3:24 PM
> To: filepro-list at lists.celestial.com
> Subject: Re: Browse Lookups
> 
> 1) Before your lookup, do a SHOW (or other NON-blocking) text display.
> 
> 2) Set an increment counter to zero.
> 
> 3) Every time that code block is executed, increment your counter.  If you want to handle it in multiples of 'x', do the calculation to determine if you're on that multiple (of, say...100 or 1000).
> 
> 4) Every time it's time to print the message, update it with the incremented counter.
> 
> 5) After the lookup is complete, take down or otherwise paint over your text display.
> 
> 6) Profit.
> 
> m->
> 
> On Mon, Jun 25, 2018 at 03:06:24PM -0400, Scott Walker via Filepro-list thus spoke:
>> I'm doing a browse lookup.
>> 
>> There is some code executed for each record which causes many of them 
>> to be dropped  (that is good).
>> 
>> But when a lot of records are dropped (like thousands) I want to flash 
>> a message telling the customer that the system is doing some searching 
>> and is not "frozen".  When the system is not actively searching for 
>> records to include, (like when it's filled up the entire browse lookup 
>> window) I want this message to be cleared or when it's gotten to the 
>> end of the file it is searching through.
>> 
>> Has anyone figure out how to do this?
>> 
>> I'm having trouble figuring out where the right place to put the code