|
Wise advice grasshopper. And use SQLSTT, not SQLCOD. SQLCOD is kind of deprecated. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Buck Calabro <Buck.Calabro@xxxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 04/08/2003 01:39 PM Please respond to RPG programming on the AS400 / iSeries To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> cc: Fax to: Subject: RE: SQLRPG - Fetch Into a record format? As Rob pointed out earlier, one decided difference between SQL and RPG native access is that native uses an exception model but SQL uses a return code model for errors. That is, if things go casters-up, native will throw an exception and kill the program (think library list, authority failure, allocated file, etc.) With SQL you, the programmer MUST check the return code (SQLCOD or SQLSTT) to determine if your operation was a success. My advice is to check SQLSTT after every SQL operation. --buck _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.