RE: Check constraints was: Imbedded SQL vs Sequence object

Joe,

How would one check against the WRONG customer in a batch feed (like from
EDI) that couldn't be done with a trigger? Even interactively, in a
server program, you have to remain interface neutral (so a standard pop up
of "are you really sure?" doesn't fit the bill). After all, the same
server program could be used from 5250, VARPG, browser, etc.

I am trying to fathom how, and even if I use "Gee, we only allow customer
12345 to be used if they are ordering 'XYZ' via EDI on PO '456'" I still
think that would be as easy to handle in a trigger as on a server program.
If I really stretch the imagination I suppose the interface to the server
program would be some huge undelimited data structure that allows for more
and more fields to be used in the undefined space to supply more data to
the server program as time goes by. Like customer number, item ordered,
call stack, PO. Granted, call stack can be determined, but may be all
those fields are not easily accessible from a trigger. Then again the
documentation about the use of the datastructure can get quite ugly quite
fast. The developer calling that server program then starts wondering
what parameters are required or conditional or reserved for future use,
and if I got to put that kind of thought into it, why can't I just update
the data already - heck fire, I've already gone through that much editing?
And part of me still thinks that if the developer can gather that
information then surely the trigger can also.

Rob Berendt