I'd say it depends...
I have seen code, even from "experienced" developers, that did not even 
know that SETLL or READ existed.  To read a whole series of line items 
they would chain by a combination of order number and line number, 
starting the line number with 1 and incrementing until the chain was 
unsuccessful.  To me, that is an excellent area to replace chain with 
setll/read.
<opinion>
It would take an awful lot of convincing for me to wholesale replace all 
chains with SETLL and READ.  And, I'd bet big money that there are those 
on this list that would argue that if you are going whole hog to replace 
CHAIN's then why replace them with SETLL and READ vs SQL access.  (right 
Mr. Odom?)
</opinion>
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 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.