>>This is kind of what I have done. I have recreated these methods as part of the application class, so that I can save when the app is destroyed and restore when the app is initialized. However, this 'seems' too late in the game.>
>
>At what point are you saving / restoring?
>
>>Also, another 'weird' thing is happening when I use the application's saveposition() that I created. It is essentially the same as cbaseform's saveposition, except the references are different, and I sporadically get GPF's (alias C0000005). When I disable this code, I don't get the C0000005 error.>
>
>You'll find there are a few different ways to generate this error in VFP6. For example, Microsoft's Knowledge Base says the RemoveObject() method can cause this problem. I've noticed that RemoveObject() can cause this error in more situations than the KB article suggests.
>
>At any rate, you can check the KB articles and see what you might be doing in your code that is generating this error.
>
>Regards,

Hi Kevin,

I am currently restoring from the Init() and saving from the Destroy(). I think my main concern is how to get the application to restore without the user seeing it resize. I think I have found the answer for this: SCREEN=OFF in my configuration file, and once restored I can set _screen.visible = .T.

Can you think of a better way to do this?

Thanks,