RE: Anyone using the *AFTER *READ Triggers in V5R1/V5R2?

Joe,

Bull.

It was a simple statement.   It was not delivered as an everywhere,
everytime, everybody piece of advice.
All this stuff is FWIW value only.

You don't like SQL,  don't use it.
I might not have multilingual environment,
Maybe the way I use it I don't give a rip if it's not flexible.
Thats my call.

Maybe I'm using wrappered SQL I/O modules.

I like SQL,  I use it. I am weighing much more towards it than DDS for Join
views, Complex views involving Group By, with things like department totals
all calced on a single fetch.

I don't give disclaimers.  They are implicitly inherent in an open forum.

off soap box.

Respectfully
John

-------------------------

> From: jpcarr@tredegar.com
>
> CREATE VIEW clearview
> As Select
> Ordno,
> CASE  Status
> When 'O'  Then 'Open'
> When 'C'  Then 'Closed'
> End
> AS Status

I'll put my piece in once, then get out of it.

Unless you're prepared to go whole-hog and redeploy all of your business
rules in SQL, I would caution against doing something like this.  Why?
Well, because it isn't very flexible.  This particular example fares very
poorly in a multi-lingual environment.