Re: Help needed on SQL*FORMS30

In article <1993Mar5.172257.24143_at_cbfsb.cb.att.com> you write:
>I have a field with an L.O.V. and there is a Key-NXTFLD trigger on
>it that anyalyses the user entry and goes to a different field
>depending on the value. The users have requested that they not
>have to enter a carriage return after double clicking on a value
>in the L.O.V. window. This sounded reasonable so I looked into it
>and found the following:

You can write a KEY-LISTVAL trigger on that particular field and in thhe trigger you can write all your stuff which you might be writing in KEY-NXTFLD trigger.

>
>1) The manual says that the POST-CHANGE trigger will fire when
> "an operator reads a value into a field from a list of values".
> Not true - I turned on the DEBUG mode and the POST-CHANGE
> trigger does NOT fire until you leave the field.
>
>2) The second problem is an old one. The completely arbitrary
> (as far as I'm concerned) division of packaged procedures
> into "restricted" and "unrestricted". Even if the POST-CHANGE
> trigger fired when it is supposed to - it will not run
> "GO_FIELD" and it will not run the Key-NXTFLD trigger since
> it contains "GO_FIELD".
>
>Another problem, which I cannot find addressed in the manual
>is "overwrite". For example, if a field is populated and you
>want to replace the value, you cannot simply overwrite the value.
>You have to backspace over the existing value and then enter the
>new one. If the cursor is at the start of the field (as it
>often is) you have to use the "right" key to move past the field,
>*then* backspace and enter the new value.

Please check whether char mode is "INSERT" . If it is, then you will have to do like this only as field would not accept any thing more than its length. Just check it as I never faced this problem when Char mode is replace.

Sanjeev
>
>
>
>
>marc colten
>
Received on Tue Mar 09 1993 - 01:27:33 CET