Re: URGENT - LOV excess!
Date: 1997/05/21
Message-ID: <33832d6b.1344783_at_news.logica.co.uk>#1/1
I've encountered a similar senario....
The problem can be solved in two ways
- Limit the number of records returned by forcing the user to enter
a partial value in the field that the Lov is on..
If the field was called :Block1.MY_LOV_FIELD (type char) then make the query text of the Lov as follows :-
Select Field_Name From My_Table
Where field_name LIKE :Block1.MY_LOV_FIELD||'%'
Create the following trigger on the Lov field
(Key-Listval)
DECLARE
l_ret_val NUMBER;
BEGIN
IF :Block1.MY_LOV_FIELD IS NULL
THEN
Message ('enter a partail value');
ELSE
l_ret_val := show_lov ( 'My_Lov' );
END IF;
END: I've used this technique on tables with approx 96000 rows and it work pretty quickly with an indexed column.
2. Create a form based on the Lov. The form will only fetch the a few rows at a time and provides better search facilities.
On Tue, 20 May 1997 08:54:57 +0200, Angel Perez <cesinsl_at_redestb.es> wrote:
>Hi all!
>
> We are in a big hurry to find a solution to our problem: does anyone
>knows how to limit the number of rows a LOV gets from the database? I
>mean, we've got an articles table with up to 11000 rows, an when we use
>a List Of Values to make an order, for example, it takes too much time
>when retrieving them from the DB. So, we thougth about limiting the
>number of rows recovered from the DC to 1000 a time, retrieving the
>others if the user needs them. Is it possible? Are we fools? Is there
>any other way to implement a LOV and making it really useful?
>
> We will be very pleased if someone can give us a light!! Many thanks,
>
> P.D.: We have tried the "Long list" property, but we don't like it,
>too much technical for an end user...
>
> P.D.2: Please, answer by e-mail also if possible
>
> Rafa Flores Yoldi
> cesinsl_at_redestb.es
Received on Wed May 21 1997 - 00:00:00 CEST
