>>>>After running my .app inside vfp a few times and trying to edit a form, I get "GDI memory is low, close one or more windows and try again" which started happening after I added a menu and changed the way my forms load and release. My cleanup has CLOSE DATABASES ALL, CLEAR, CLEAR WINDOWS, SET CLASSLIB TO, CLEAR ALL, RELEASE ALL, SET SYSMENU TO DEFAULT, ON SHUTDOWN. But I get the feeling that something is not closing. I don't know what GDI memory is. What am I missing?
>>>
>>>That's your graphical device interface (windows) memory. I had trouble back in 2.6 with it...if you do an MSKB search on GDI, you'll find a number of articles on problems with GDI...
>>
>>As I remember, non-standard and quite-big fonts used to eat GDI memory.
>I don't have any of those. The MSKB mentions GDI leaks related to scrolling data environment windows or moving form designer windows, but nothing specific to the change I made. It started happening to me when I put a menu and a read events in my app. I get the error when I've run my app a few times, editing forms between each run and recompiling. The workaround they mention is to quit VFP, indicating that a compiled .EXE shouldn't cause my users any problem.

Are you using Windows 3.x? I run into this problem frequently at work particularly with large Excel spreadsheets that are constantly loaded, closed, and reloaded again. I don't think Windows 3.x gives all the memory back in this type of scenario so I end up having to reboot my PC.

Good Luck,

Bill Chadbourne
wchad@ime.net