Re: Triggers

Now you raise an interesting point... could the trigger program retrieve a
piece of information so that it'd know if it is a green screen or not? 
or, monitor for a message?  If green screen, continue; if not, send a
message to the user and/or the QSYSECOFR?

In <35DFA0C4.3E74CB0F@wt.net>, on 08/22/98 
   at 09:55 PM, Bob Larkin <blarkin@wt.net> said:


>Booth
>2. You will have a mess.I am assuming the Non Green Screen app is not
>simply a GUI session (ie. Seagull's GUI/400). We have VB applications
>that update AS/400 records using SQL packages. The trigger fires, then an
>error code is set if the trigger does not like the record. The PC
>receives an indication that the record was not written, with an SQL code
>to describe the error. There would be no interactive session associated
>with the I/O request, so the program would fail. Bob

>boothm@ibm.net wrote:

>> When one puts a trigger on a physical file:
>>
>> 2-What happens if a field is accessed/changed with a non-green screen
>> application like Access if the trigger validates a field, and if invalid,
>> starts an interactive window displaying valid choices?  (There is a file
>> that is used in a very elaborate and integrated purchased package.  We
>> want to validate a few fields in the file against acceptable responses in
>> another file.  A trigger does that very nicely.  We don't access the file
>> with any non-green screen applications now, nor do we plan to, but we are
>> wondering what would happen if the future changed our mind.)
>>
>> tia
>>
-- 
-----------------------------------------------------------
boothm@ibm.net
Booth Martin
-----------------------------------------------------------

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---