🚀 go-pugleaf

I guess what I was trying to get across was .. when developing
screens under Oracle's SQL*Forms some of the underlying procedures
and triggers are generating for you.  The error checking/data
integrity/etc. are handled automatically with in Oracle and not
within PowerBuilder (which has to be programmed manually by the
developer).  So when coding with PowerBuilder you spend more time
writing code that Oracle handles with in the kernel (built in procedures,
triggers and functions that require no coding).

>[... snip ...]
>
>>Oracle is telling us that to develop the same screen with the error
>>checking and data integrity checks in SQL*Forms is a no-brainer but
>>using PowerBuilder for example would require pages of C code.  I've
>>heard this before but not from Oracle rather from other developers.
>>
>I'm curious. I've been fiddling with Powerbuilder for about 9 months now -
>mostly to WATCOM sql but we also have MS SQL Server. What kinds of error
>checking are you referring to? Is it resources checking i.e. "do I have
>enough memory to open this window"?
>
>Dean
>
>----------------------------------------------------------------------
>Dean Burnfield
>Programmer/Analyst
>The University of Texas Health Science Center at San Antonio
>burnfield@uthscsa.edu