Validate from List property of dynamically attached LOV

Question

Dear Oracle Gurus,
I have multi record block , the fields are Argument_name,Argument_Code ,argument_lov
displaying two fields . data is populated at run time
user has to input for the argument_value according to the argument_name displayed
it may look like
Argument_name Argument_value
Date of Join User has to input
Branch office user has to select from a LOV
Dept User has to select from a LOV
the LOV's underlying Select statement will fetch data from a table based on other field Argument_Code
The LOV is attached dynamically for each row based on a value for the field argument_lov value will be Y or N
IF value for a argumet is Y , the LOV is attached with SET_ITEM_PROPERTY in the When NEW RECORD INSTANCE Trigger
when user moves to the argument Date of join there will be no lov and the user has to type out the data
whereas for the argument Branch Office , user can select from a LOV
now the user has to press the F9 key to invoke the Lov and then select
whereas we wanted in this way.. that the user can type the first character and the value automatically get selected
if the user types wrong data then the LOV to be displayed
For this we used the SET_ITEM_PROPERTY with VALIDATE_FROM_LIST, Property_true in the same trigger.
we have record validation trigger at the block level .
But it didnt work out exactly when ever the user moves from a record having LOV after selecting. the other field which is not having a LOV displays a lov with values belonging to another field and asks to select from the list . For example the date of join field displays the lov for dept and asks to input
please guide me in this regard
with warm regards
ssr

Answer 1

But when table hav too many rows (here i hav 18000 rows) getting too slow....Is this problem is common...? Yes, this is common when you have a lot of rows returned by your LOV query. In situations like this, it is best to try and reduce the size of the data returned by your LOV. One way of doing this is to enable the Filter Before Display property on the LOV. When enabled, it causes Forms to display a query criteria dialog before displaying the LOV. This too can cause slowness because this option could cause a full table scan to occur. Perhaps a better option would be to make your LOV dependent on other limiting values. For example, if your Form showed a list of all employees in a company you could make your user select limiting data like a department number to help reduce the number of employee records returned by your LOV.
Craig...