Re: Forms 4.5 LOVs

The block.item must exist for the LOV to do the mapping. Another solution is to wrap all your lov calls so they return their values into globals, then assign the globals to the proper fields. This eliminates the problem when a user who doesn't have update privilege tries to use an lov to see values, then gets an oracle error upon closing/selecting. Of course, you could always map another LOV to the item that doesn't have any return items (ie. a "query only" lov vs. one that returns data).

"Joyce A Moore" <jm5h+_at_andrew.cmu.edu> wrote in message news:Mtx9CBK00Ui_06N100_at_andrew.cmu.edu...
> I'm developing forms in Forms 4.5, using the template that comes with
> the Oracle Apps. Every once in a while, a form starts rejecting LOVs,
> saying that it can't map the fields. (I had the form and these LOVs
> working before, but have made some changes to display canvas, tabbing
> order and such.) If I save the query and remove all reference to that
> LOV, I can then recreate it with the same name, query, and field mapping
> and Forms is happy again. Does anyone have any idea what causes this?
> It is usually only one or two LOVs, but this time it was 5 and is
> becoming annoying. This time all the record groups used a query that
> hits the Apps value set tables, but that may be only a coincidence as
> most of the LOVs in this form are like that. The last time it happened
> it was other tables.
>
> Joyce
Received on Sun Oct 29 2000 - 19:22:02 CET