RE: CHAIN Versus SETLL and READ When Data Needed

What was really confusing was when I tried to do stuff like
DoU F3
  or shutdown
  or Moon="Blue"
  or ...;
Which is why people code 
DoU KissOff;
and then just turn KissOff on if any of those conditions are met.
Still I think the iter can be clearer than having to code a crap load of 
IFs around every condition.

You know what is really cool?

DoW CheckItAllOut();
  // no logic here
EndDo;


Think about it.
No priming reads needed on a SETLL/READ loop.
No priming FETCHs needed on a cursor.

DoW FetchCursor();  // Actually fetches the row.
or use
DoW ReadLoop();  // Does the actual reading of the file
  // main body of loop
EndDo;

And your subprocedure could handle the really obscure stuff like intense 
error trapping that most people fail to do because it would clutter up the 
main code and the odds of it ever happening are slim to none.

Rob Berendt