>>>What does it hurt to put a SELECT before an ENDSCAN so that it is clear to **any** reader what is being done?...
>>
>>The maintainability of the code decreases and the risk of bugs increases.
>
>In an era of FIND/REPLACE and mouse scroll wheels this is a weak argument at best. In the meantime the reader gets a nice reminder of which area is current. For any reader to be bothered by that is, to me, surprising.


FWIW, Jim, it would never occur to me to search for a SELECT at the bottom of a SCAN loop. So Find/Replace wouldn't help me in this situation, unless I were changing every reference to a particular table. Of course, the extraneous SELECT to the wrong table wouldn't keep the SCAN from working properly, but it sure would make reading the code more confusing.

Tamar