When closed, does a substack whose destroyStack is true remains in memory ?

[Martin Blackman]

The original thrust of this thread still puzzles me a little - how
does one satisfy the requirement stated in the docs that a stack be
closed and not in memory before setting 'formatforprinting'  to true ?
  eg a typical application has a printing substack that gets cloned
(thereby opening it) and filled with data before printing.  I can set
formatforprinting to true before cloning, but then the text fields
will be edited before printing -which is also a no-no according to the
docs, if I understand correctly.

Martin Blackman