×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I think it's a bad idea to have the trigger program attempt to display any
kind of UI...
I tend to agree. Error handling in applications offer things like setting
focus and highlighting fields that are in error, changing an icon on the
screen to indicate the type of message (Error, Warning, Successful
completion status), offering a hover effect to provide extended help text.
I'm very seriously considering changing our application architecture to
implement data validation and RI constraints in Triggers. But I wouldn't
want to lose any of the benefits and usability that applications provide in
terms of error handling.
One should also be mindful that the application might be ILE, Java, .Net,
PHP, Ruby, Perl, Windows PC, etc. You can't expect Triggers to support
every conceivable UI option.
I might make an exception in the case of Triggers evoked by 5250 utilities
such as DFU, STRSQL, etc. by optionally displaying a Window Overlay in
connection with an *ESCAPE message.
But I still believe that Triggers should prevent invalid data from getting
into the database.
Nathan.
midrange.com
