Re: Navigating Detail Records

Hello Daniel,
 You are quite correct, a block level trigger does only fire when you enter of leave the block. However, as you want to validate records (or screen items) then why not put your trigger at the item level instead of the block level?

In the forms navigator, if you expand the field items you will find that you can put triggers there (at item level). These triggers will fire whenever the screen field is actioned. This includes changing to a different row.

I suggest that it doesn't make too much sense to have a validate-item trigger on at block level. I suggest a validate record trigger at this level. This gets fired whenever a user tries to leave the record.

>... What I am having trouble finding is a record
>level trigger that will fire when query results are displayed and when scrolling.
>
When query results are displayed --> see POST-QUERY - this gets fired for each row returned. It is often used to put data in non-database fields. It doesn't matter whether you scoll or not.

graham

On Wed, 07 Jul 1999 12:15:41 -0700, "Daniel A. Morgan" <dmorgan_at_exesolutions.com> wrote:

>I have a field in the database with a check constraint that accepts the values R
>(red), Y (yellow) and G (green) for a stoplight charting application. The
>end-users will be looking at a Forms 5.0 front-end containing a list item with the
>values Red (mapped to 'R'), Yellow (mapped to 'Y') and Green (mapped to 'G'). So
>far so good. And the WHEN-VALIDATE-ITEM trigger works just fine when updating or
>inserting a new record.
>
>The problem is that when an initial block-query is made, or when the user is
>scrolling from parent record to parent record the WHEN-VALIDATE-ITEM trigger does
>not fire. Block level triggers affect the entire block and don't distinguish
>between the child block's records. What I am having trouble finding is a record
>level trigger that will fire when query results are displayed and when scrolling.
>
>Thanks,
>
>Daniel A. Morgan
Received on Thu Jul 08 1999 - 19:22:29 CEST