RE: SQL Embedded in RPG ILE.

>The try and catch I'm referring to is more like a
>sql failure exception.    

OK, but the same question applies, what are you going to do on the
catch? Even more so than a missing customer, a sql failure exception is
probably a fatal error. What's the point of catching it just to throw
something else, just let it bubble.

>It could return thousands of records which require caller to...

You've got a couple of options. First, don't return a recordset, return
a collection (array?) of customer objects, one for each customer found.
That's the most OO-like thing to do. Or, in the case of a recordset in
C# I can tell the recordset to close the connection when the recordset
is closed, I don't have to manage it myself. Finally, you could use
something like a DataSet, which is a client-side recordset, so all the
rows are retrieved within the FindBy function and cached on the client
and you don't need a connection to the server.

-Walden

------------
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)