Re: Date procedure

["David Morris" <dmorris@xxxxxxxxxxxxx>]

Rolf & Buck,

Your observations that moving SQL to a single program are quite different than 
my experience.  We use one program for most of our SQL and it greatly 
simplifies using SQL.  For example:

EVAL SQLHandle = SQLOpen('Select * from...': %ADDR(InputArea))
IF        SQLHandle <> *ZEROS
DOU  SQLEOF or SQLErr
EVAL SQLFlg = SQLFetch(SQLHandle)
...blablabla
ENDIF
ENDIF

Seems simpler than worrying about cursors, SQL limitations, etc.  You do 
pay a very slight performance penalty because the statement has to be 
prepared. In many cases you get this back because of the ability to easily 
manipulate data and select only what you want/need.

David Morris

>>> buck.calabro@aptissoftware.com 12/12/00 07:38AM >>>
Rolf Mittag wrote:

>That's just as I do it for now. I've a service-program for
>all Sql. But that's _definitivley_ _not_ desirable as a design
>because it makes simple things more complicated.

As you say, it makes simple things more complicated, but nowadays, what is
simple anymore?... 

Buck Calabro
Aptis; Albany, NY
"Nothing is so firmly believed as
 that which we least know" -- Michel Montaigne

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