Re: SQLFORMS 3.0 (TRIGGER PROBLEM)

From: <mkrieger_at_hayes.com>
Date: 17 Jul 92 16:44:06 GMT
Message-ID: <5783.2a66f8d6_at_hayes.com>


In article <1992Jul15.165249.240_at_falcon.navsses.navy.mil>, huynh_at_falcon.navsses.navy.mil writes:

> WHAT I DID IS THAT I HAD A TRIGGER AT THE FIELD LEVEL ("HULLNO") ON BLOCK1.
> EG. TRIGGER: KEY-NXTFLD
> BLOCK: BLOCK1
> FIELD: HULLNO
> TRIGGER STYLE: V3
> TRIGGER TEXT
> GO_FIELD('MACHNAME'); I ALSO TRIED A COUPLE OF OTHER COMMANDS;
> GO_BLOCK('BLOCK2'); GO_FIELD('MACHNAME');
> NEXT_BLOCK;
>
> WELL, THIS IS THE PROBLEM.
>
> I HAD THE DEBUG MODE TURN ON. AFTER THE DATA HAD BEEN ENTER FOR THE "HULLNO"
> THEN PRESS THE <RETURN> KEY, THE TRIGGER WAS ACKNOWLEDGED, BUT IT NEVER FIRES
> CORRECTLY. THE CURSOR INSTEAD OF JUMPING TO THE NEXT BLOCK, IT CONTINUES TO
> THE NEXT FIELD ON THE FIRST BLOCK.
> SOME TYPE OF DATA HAD TO BE ENTER TO GET THROUGH AND THAT 'S WHAT I DID. WHEN
> IT RETURNS TO THE ORIGINAL STARTING FIELD ("HULLNO") AND IF I WERE TO HIT THE
> <RETURN> KEY AGAIN, THE TRIGGER WILL BE ACKNOWLEDGE AND THIS TIME IT WILL FIRES
> CORRECTLY.
> IN OTHER WORDS IS THAT THE TRIGGER FIRES A BIT TOO LATE.
>
Check the SELECT attributes on the field you have to enter data into. The attribute "REQUIRED" needs to be turned off. This is automatically set on if the field is NOT NULL in the database.

MLK Received on Fri Jul 17 1992 - 18:44:06 CEST

Original text of this message