Re: Forms 4.5 LOV Questions.

In article <01bc50d3$51184d80$6b6482d0_at_cbcsf1.techlink.net>, Cleve <cleve_at_cbcsf.org> wrote:
>Hi everyone. I am posting this question hoping that some expert(s) knows a
>work-around...
>
>Here's my situation:
> I have a LOV called EMP (having LastName,FirstName,EmpID)
> attached to a Manager_ID field. I have set the LastName in the
> LOV as the first field so that all incremental searches will be
> on the Lastname. When a selection is made, EmpID is returned
> to Manager_ID.
>
>I need answers to the following:
> 1. If I type in a # for the Manager_ID and then 'pull up' the LOV,
> how can I get the associating record in the LOV to be
> highlighted without narrowing the search? By default, Forms
> highlights the very first record in the LOV.

I don't think there is a way. LOVs pay no attention to the current value in an item on the form. However, you can horse around and re-create the underlying record group with a different order-by when the LOV is requested. The order-by could use a decode to place the row with the Manager_ID value as the first row.

> 2. If I set the 'Validate from LOV' property to TRUE on the
> Manager_ID field, how can I get forms to validate the
> Manager_ID field with the Emp_ID column? Because the
> LastName column is the first in the LOV, Forms, by default,
> attempts to validate it against this field.

Again, I don't think you can. But again, you can code a work-around. Set the LOV for Validation attribute on the item to False, and then validate the Manager_ID in the WVI trigger. If the entered value is invalid, issue a Show_LOV command.

Good luck,
Steve Cosner Received on Fri Apr 25 1997 - 00:00:00 CEST