[RBG7-L] - Re: Form fires trigger but does not exit

[Bernard Lis]

Alastair,
Interesting.
I've been using i1,i2....ia, ib, etc
Now I can make them all i1
Thanks,
Bernie Lis
----- Original Message ----- 
From: "Alastair Burr" <[EMAIL PROTECTED]>
To: "RBG7-L Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, November 18, 2004 3:08 AM
Subject: [RBG7-L] - Re: Form fires trigger but does not exit


Bernie,
One of the things that I picked up from this list - Bill Downall, I 
think -
was to use one variable for all indicator needs. For example:

SELECT... Col_1 INDICATOR vIndicator, Col_2 INDICATOR vIndicator ...
Assuming, of course, that you don't actually need the indicator!!
Regards,
Alastair.
----- Original Message ----- 
From: "Bernard Lis" <[EMAIL PROTECTED]>
To: "RBG7-L Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, November 18, 2004 3:41 AM
Subject: [RBG7-L] - Re: Form fires trigger but does not exit


Thank you Larry,
I filled in all fields in the row so I didn't get null values and it
worked.
I also changed the select statement in the procedure to use indicators,
which lazy me, I usually don't do.
Bernie Lis
----- Original Message ----- 
From: "Lawrence Lustig" <[EMAIL PROTECTED]>
To: "RBG7-L Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 16, 2004 11:03 PM
Subject: [RBG7-L] - Re: Form fires trigger but does not exit

>> If I use a form   edit using employee where empno=116
>> it also saves the before and after rows but does not exit the form 
>> when
I
>> click exit.  Instead it just comes back to the form and I click exit a
>> second time, it saves the b4 and after rows again (but not the 
>> original
>> data) then asks "data has been changed do you want to save." then it
will
>> exit the form.
>> When do the triggers fire?  My thought is after I exit the form, is
this
>> correct?
>>
>> The exit button calls a predefined  "Save and Exit"
>
> If there is any error at all in your trigger code it will probably 
> cause
> the
> form not to exit properly.  Remember that a SELECT statement that
returns
> no
> rows, and a SELECT INTO that retrieves a NULL value into a variable
> without an
> INDICATOR variable are both considered errors.  Therefore, if your
trigger
> code, for instance, checks for the existence of a particular key value
in
> the
> journal table, it will return an error the first time through, but not
> subsequent times.
>
> You need to very carefully code that trigger so that no errors occur
> within it.
> --
> Larry
>
>
--- RBG7-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [EMAIL PROTECTED]
(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE:
Send a plain text email to [EMAIL PROTECTED]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [EMAIL PROTECTED]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body,
place any
text to search for.
================================================