Re: last_record

From: <stevec_at_zimmer.csufresno.edu>
Date: Wed, 12 Aug 1998 15:54:13 GMT
Message-ID: <6qsdr5$lhm$1_at_nnrp1.dejanews.com>


In article <RgKz1.11$J3.956602_at_nnrp2.ni.net>,   "Michael Toomey" <michaelt_at_americanrecruitment.com> wrote:
> One of my forms 4.5 modules is likely to be required to support
> large queries (ie. 2000 - 3000 record returned). users will
> browse through these returns one at a time or 25+ at a time.
> initially, i had four buttons on my toolbar:
> << < > >>
> back 25, back 1, forward 1, forward 25

I just use the up/down arrow keys and the PageUp and PageDown keys.

> defined as:
> go_record(to_number(:SYSTEM.TRIGGER_RECORD)-25);
> do_key('up');
> do_key('down');
> go_record(to_number(:SYSTEM.TRIGGER_RECORD)+25);
>
> i found the performance to be miserable when scrolling back
> 25 records at a time.

I'm not sure why scrolling back is so bad. It is the forward scrolling that takes the time--your form has to fetch another batch of records. In my forms, scrolling up a page at a time takes no time, but scrolling down does.

> figuring that i had to play with the "records buffered" and
> "records fetched" settings, i tweaked them every way to
> sunday and had no significant performance gain (unless i
> set them to 999, which will never cut-it on some of my
> small client machines).

The time is probably related to both network speed as well as client processing speed. I have noticed on clients that the farther down you page into your query, the longer each successive page-group takes. There is something really inefficient going on in Forms.

> fallback option was to abandon the +/- 25 records idea
> and change to FIRST_RECORD and LAST_RECORD.
>
> new problem is that LAST_RECORD takes minutes to
> complete. this seems crazy ... the initial query takes
> about .25 seconds to complete.
>
> so, questions:
> - Is LAST_RECORD useless when you have a large number
> of queried records?

Yes. Last_Record causes the form to fetch all rows of the query into the client, which takes all the time.

> - Is there some parameter that i can change to fix either
> of these problems?

Don't know of any.

If at all possible, it would be best to do something in the form so your query would only retrieve several hundred rows max.

Steve Cosner

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum Received on Wed Aug 12 1998 - 17:54:13 CEST

Original text of this message