>Frustration, anxiety, and not really wanting to toss the computer out the window prompts me to send a question out.
> VB5 keeps stuff in the temp directory and after time, the temp directory gets huge and VB5 doesn't like to open up and work properly, eventually not opening at all. A real "Laser" pain!
> I'm having similar problems with VFP 3.0 I'm only getting a quick flask of the opening screen (<1sec) then a msgbox stating "Insufficient Memory". that's it, no error code just the works in the msgbox. VFP 3.0 will not open whereas VFP 6.0 opens just dandy! My physical memory is 256MB and virtual is over 500MB. Question, does VFP 3.0 have the same storage of temp stuff somewhere as VB5 does? My C:\temp directory is clean.
>Comment??

I wouldn't rely on the error message that Fox displays to be exactly the cause of your problem - more like a suggestion.

You seem to be referring to both RAM and Hard Disk above. With regard to RAM - this should only be a problem if your swap file size is inadequate and you have a large number of memory hungry apps running. On the hard disk front, check the systems folders (c:\WinNT, etc.) and also the application directory itself - these can also accumulate .tmp files. If your app does not have access to a temp folder, it might use the app folder. I've experienced problems in the past where temporary files on a NetWare server were actually causing problems after they had been deleted - solved by running purge.

Hope this helps.