RE:SQL: Error handlling (was SQL UPDATE question

[jpcarr@xxxxxxxxxxxx]

How about something like this?   If the code is greater than zero,  But not
100 an SQL warning error happened.
Maybe you were putting a character field into too small of a target field,
The warning error might tell you
that some info was truncated.  In certain cases you may say  "I'm ok with
that"  so maybe not a HALT error
for you in that case.


In the case it's negative, you can get the SQL code (you can even concant
it with 'SQL"
and look up the message in QSQLMSG message file).



C         Select
C         When SQLCod  <  0
C         ExSR SQLError

C         When SQLCod = 100
C         ExSR NoMoreRows

C         When ( SQLCod  >0  Or SQLWn0 <> *Blank )
C         ExSR SQLWaning

C         Other
C         ExSR ProcessRow
C         EndSL



John Carr

------------------------------------------------
    * Check after each SQL statement to make sure
    * it executed as expected
   C              if    SQLCOD <> SQL_OK
   C              exsr  SqlErrorHandler
   C              endif
Pete,
I would like to know more about your SqlErrorHandler routine (if you don't
mind).  Right now I watch for 100, and not 0 or 100, to identify errors.
If
the sqlcod isn't 0 or 100, I assume something unrecoverable happened.
Phil





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