Re: LOV crisis

Dennis,

At a guess the code is the first column in the LOV when the 1st column must be the description. It pops up inconsistently because the values for code and description are sometimes the same (?).

Dennis M. Hancy <dw724_at_cleveland.Freenet.Edu> wrote in article <6hpue8$mm7$1_at_pale-rider.INS.CWRU.Edu>...
>
> I have a form with a block that contains several fields. One of these
> fields is a "code" field that is a base table item. Another field is a
> "description" field that is not a base table item. My goal is to not
> have my end user see this Code field. Instead, I want to look up the
> Description in an external table based on the value in the Code field.
>
> To make this work, I will need two things. First, I created an LOV that
one
> can use to select a Code when entering a new record. Secondly, I created
> a Post-Query trigger on the block that is used to populate the
> Description field from the Code field when a record is queried.
>
> When I now run my form and query up records, I have a problem. Some
> records display normally; however there are a few where my LOV pops up.
> I have the LOV for Validation property set to True, so my first thought
> was that the code in my base table did not match one of the codes in my
> lookup table. However, I can see in the background that the proper
> Description is already filled in. Yet, this LOV is displayed on top
> of my form.
>
> Any ideas as to what's causing this behavior? You can either email me
> or post a response to this message. Thanks in advance for any help.
>
>
> Dennis Hancy
> Eaton Corporation
>
Received on Mon Apr 27 1998 - 05:28:17 CEST