>Yeah, but that doesn't help to figure out why the var is not being saved!

I would be surprised that the command would still work. It was designed for character mode screens, then screen areas - but not for pixels. It's still there in the syntax tables, but I guess it was off the testers' checklists many versions ago. I'd gave expected the Restore Screen to ignore the variable, i.e. to be basically a no-op just like Save Screen is, but it seems to require a variable of type "S" which can't be produced anymore.

Obsolete, not in use anymore, and there are no plans to reintroduce it.

You may play with screenshots, though - bitmaps which would contain the previous contents of a window/form, and set the saved image as the form.picture (even if you're running in a Define Window, give it a Name clause - and the object you get is a form), or have an image object at the bottom of the z-stack with that image as .picture (in the probable case when this saved image will contain the borders, caption, close box etc, so you'd want to move that under the rug, i.e. set the .top and .left of this image object to some small negative values). But keep in mind that this is just an image object, and that it's an object, i.e. it will have to be either covering your @get objects or be covered by them (it will go over @says because they're just painted, IIRC), depending on the order of instantiation and calls to .ZOrder(). So... if this guy is already asking you to do this, he's already modernizing the app. So why stay in the @say/get world? There are converters available here in download section, may be simpler to do that than to mess with writing window management emulation from scratch.