>>>>>>I have SET RESOURCE ON, VFP6 tells me this if i test the following commands:
>>>>>>
>>>>>>? set('resource')
>>>>>>ON
>>>>>>? set('resource', 1)
>>>>>>C:\PROGRAM\MICROSOFT VISUAL STUDIO\VFP98\FOXUSER.DBF
>>>>>>
>>>>>>So what wrong? And the problem is only with .prg files, forms and reports for example works fine. Maybe but I'm not sure can it be Visual Studio SP3 that causes the problem? It's around the time when I installed SP3 that the problem starts...
>>>>>>
>>>>>>/Mårten Törnquist
>>>>>>
>>>>>
>>>>>That's your problem. It's a bug in SP3.
>>>>
>>>>My VFP6/SP3 keeps my .PRG windows just fine. What do you mean there's a bug in SP3?
>>>>
>>>>Mårten, you could try reseting your properties for a .PRG editting window by editting a .PRG file, choosing the Edit Menu/Properties and check the "Apply to .PRG Files" checkbox. If that doesn't work, try deleting your FOXUSER.DBF/.FPT and letting VFP create a new one for you.
>>>
>>>
>>>Maximize the edit window in a method. Then run the form. When you go back to the edit window, it will no longer be maximized.
>>
>>Actually, I always found that to be annoying. BTW, mine does not work as you describe. It stays maximized. What I do find annoying (still), is that if you have a method expanded, and then you open another method, it's expanded, too. To each his own.
>
>I have the same problem as Mårten since I installed SP3
>.PRGs won't stay maximized.
>I already deleted FOXUSER.DBF and re-applied the Edit properties to .PRG files as I usually do when FOXUSER becomes messed but it didn't work.
>If it is a SP3 Bug as Craig says it is really a very annoying one.
>If someone ears about a solution please let everybody know.
I don't really think that it's a SP3 bug. I guess what it is, is that I don't really use the maximize button to change the size of the edit window. I just drag the edges to be the size I want it to be. It seems to keep the size OK that way. I seem to remember that was always the way it worked, even in FPW, that a maximized .PRG window (with the maximize button) did not retain it's size. Still seems to work that way in VFP6/SP3. I've gotten so used to doing it that way (dragging) automatically, I just don't think about it anymore!
