>Ernie, this information is saved in your FoxUser.DBF. If you have SET RESOURCE OFF then it will not be recalled when you start VFP again. If you DO have SET RESOURCE ON, then try PACKing your FoxUser.DBF. That may help.
>
>HTH
>
>
>>I cannot figure out how to get my Debugger to open up the way I want it to. I'm using VFP5 and whenever I set step on in my code, or get an error and so suspend and VFP opens the debugger, it always comes up in a way OTHER than the way I last left it. I've tried saving the configuration (file1.dbg) and then tried loading it but no diff.
>>
>>Example, VFP opens the debugger for me (the way I don't want it.) I move windows around, resize the app area, etc., then I use SAVE CONFIGURATION off the File menu and give it a name "MyConfig.dbg"). For as long as I don't close the debugger, the settings are fine. If I close it. Then open it back again, it reappears the way I don't want it. So I say LOAD CONFIGURATION from the menu, pick "MyConfig.dbg" but it has no effect.
>>
>>Help was not helpful. Am I missing something? Is there also a way to maybe set a default in CONFIG.FPW ... or in the registry (which help alluded to.)
>>
>>Any help greatly appreciated.
>>
>>Annoyed and getting frustrated ...
>>
>>Ernie

Aha! Thanks Barbara, that did the trick. It seems the framework I use (Visual Extend) sets resource OFF so when I open the debugger from within my app via SET STEP ON or something, it opens in what I guess is VFP's default. (Gee wouldn't it be nice to be able to change THAT.) Then, when I exit my App, the frame work sets resource back ON. (Subtle. Very.) So if I close the debugger now when it's in VFP's no-resource default, VFP is saving its own defaults in FoxUser as though they were mine. Not.

Wow but you really have to stay awake with VFP. You can't be to sure who, what, or when something is happening behind the scenes.

That understood, it explained what "LOAD/SAVE CONFIGURATION" in the debugger was all about ... save the breaks, parameters, locals, or watch variables you're debugging ... NOT the window positions. After figuring out what was happening, NOW I know how these are used. (H'cum VFP Help doesn't explain this stuff better?!)

I appreciate your help. Thanks all.