>Quinn,
>
>[dregging up old memories] I used to use the SAVESCREEN mechanism to 'pop' the
>FPD screen back to it's original state after having to perform some
>intermediate behavior. When I moved to FPW, I found it better to leave the
>screen in memory. If you want to emulate the "disappear/reappear" look in FPW,
>use the HIDE WINDOW/SHOW WINDOW commands. If you don't care if the screen
>stays visible when you switch to another screen and back, you only need to deal
>with ACTIVATE WINDOW/DEACTIVATE WINDOW commands.
>
>>I have a problem with a window that comes up saying insufficent memory. Our
>>program was originally written in FPD 2.0 and we are currently converting it
>>to fpw 2.6. When we use the command savescreen on the menu it bombs out saying
>>insufficent memory.

Savescreen was also used by people who either did not understand how to use windows or for whatever reason did not want to use windows. I see it around here in Clipper converted to FPD. The best fix is to convert the screen to a window. Makes for much 'neater' apps.