Re: post-change and on-validate-field trigger

In article <3rplvc$nek_at_gaia.ucs.orst.edu> mickel_at_OES.ORST.EDU (Paul Mickel) writes: >In article
<1995Jun15.111247.26439_at_newton.ccs.tuns.ca>, <James Richard> wrote: >>In article <3ri50q$70a_at_artecon.artecon.com> quach_at_ext423.artecon.com (Phuong Quach) writes:

>>>Hi all,
>>> I'm still confusing on POST-CHANGE and ON-VALIDATE-FIELD.
<snip>

>>I'm not sure why ORACLE added the ON-VALIDATE-FIELD (and others)
>>trigger. My guess is for logistics reasons. So I complied.
>>
>>I use ON-VALIDATE-FIELD for checking the validity of the current field,
>>and use POST-CHANGE to affect any changes to other fields.
>>
>>James Richard (JRICHARD_at_TUNS.CA)
>>"No Assembler Required!"
>
>My understanding of this (I heard this from one of our senior developers) was
>that the POST-CHANGE trigger was a hold-over from SQL*Forms 2.3 (not sure if
>this is actually true or not). I use ON-VALIDATE-FIELD for field validation,
>and do not use POST-CHANGE at all.
<snip>

More on ON-VALIDATE-FIELD (and also WHEN-VALIDATE-ITEM):

Has anyone noticed that when you clear a field and then use Shift-Tab to do a previous_field out of a field, that ON-VALIDATE-FIELD does NOT execute? It executes only when you leave the block or commit. In all other cases, it executes when you leave the field. This happens both in Forms 3, and 4.5.

Is this a bug or a feature?

Steve Cosner (stevec_at_zimmer.csufresno.edu) Received on Thu Jun 15 1995 - 00:00:00 CEST