Re: Designer 2.1.2: Wrong code generated for LOV record group?

Roy Brokvam wrote:

> If I define a where-clause in a Lookup Table usage, the Generate Forms
> utility puts my clause into the generated record group for the LOV.
>

Roy, you _are_ aware of the fact, that there are two places to define where clauses? Since V2, you can add a 'Where clause of Query', but also a 'Lookup Validation Where Clause'. Wonder what you have where?

> My problem is that the generated clause contains two mutually exclusive
> parts; one part for Enter-Query mode and another for Normal mode; and my own
> clause goes into the Enter-Query mode part only.
>
> The result is: At runtime, in Enter Query mode, the LOV contains only the
> restricted set of lookup records; in Insert/Update mode, the LOV contains
> all the lookup table's records. I don't want the LOV to show values which
> should be rejected on insert/update! As the LOV is used for validation, too,
> the generated application does not reject new records which violates my
> restriction!
>
> Versions:
>
> NT4 SP3
> Designer 2.1.2 / Form Generator 5.0.24.3.0
> RDBMS 7.3.4.0.1
>
> Grateful for any help.
>
> Regards,
>
> Roy Brokvam
> roy.brokvam_at_conax.com

--
Frank van Bortel

Technical Consultant Oracle
V&L Informatica BV
-------------------------------------------------
Work                                Home
Postbus 545                         Hunzestraat 4
7500 AM Enschede                    7555 WB Hengelo
(31)53.434.1500                     (31)74.242.5046