>Been there, tried that, and more.

But perhaps not tried enough<bg>

>The CLEAR ALL statement would wipe out all by control variable that drive how the build is performed.

Not necessarily. It will wipe out variables and even objects added to screen, but string properties of _Screen survive:
you can daisy-chain calls with clear all after setting the necessary info to a _Screen.cSpecialXml for instance. Thus you could your cleaning before each *single* project build and read the info on what to do in the next build cycle from there. A more simple plan is to persisit in between to disk.

worked for me in different scenario, but the approach you described to Sergey also looks interesting<bg>.

>

>CLOSE ALL
>CLEAR PROGRAM
>CLEAR PROGRAM    && sometimes first does not get them all.
>CLEAR RESOURCE
>SYS(1104)        && clear the cache
>

regards

thomas