>>>>>

>>>>>SELECT alias
>>>>>SCAN
>>>>>

>>>>>is helpless, if workarea is changed in between.
>>>>> ¯\_(ツ)_/¯
>>>>
>>>>The last sentence is wrong, Scan will take care of changing the work area back to the correct one.
>>>
>>>ENDSCAN will. Altered between SELECT xxx and SCAN, SCAN knows nothing about the area selected.
>>
>>OK, I chose my words badly. If you really want to screw up you code, I think almost every command can be used. :-)
>
>It was only to show that for some stuff there is no way out. There is no help in aliasing or IN. But it is very, very rare. I know about it - but never run into it. And not all code is as clean as it should be.

Or to say it the other way around.

For code that is long running in an environment prone to that, it might be better to create something to stop (timer) events, block access to UI and so on then fiddling with half solutions like REPLACE IN alias. Or just let it run in a DE that will not be harmed by events.