>>>SELECT TableA
>>>SCAN
>>> do something
>>> SCAN while something
>>> do somethingelse
>>> nRec= RECNO()
>>> ENDSCAN && TableA
>>> GO m.nRec
>>>ENDSCAN && TableA
>
>Yep, and as J Booth said, as long as you understand what is happening to the record pointer, there is no problem. Speaking of strange record pointer behaviour did you see the post on where
>LOCATE RECORD xxx
>ignores the current filter condition. Sort of surprising. Again it not something I'd ever use but the guy wanted a way of quickly getting to the next record with a filter set. GO RECORD xxx certainly ignores the filter (and rightly so) but LOCATE in every other instance obeys the filter setting.

Seems to be that RECORD clause ignores all Filter, Set Deleted and Set Key settings currently in effect, regardless of the command with which you use it. It would be interesting to try it with commands such as Delete, Replace, Recall, Report Form and any other command which has a scope clause. Not now, it's 2AM and I'm trying to read myself into sleep :).