>>> snip <
>> I could guess that the creation and destruction of the objects is causing memory to become fragmented over time. Creating them once and leaving them there until you are really done with them would be a more solid approach (at least as far as internal memory management goes).
>>
>>Let me ask Edward Johnson's question again. Is there a low level API that compacts the heap and would that fix this problem of memory fragmentation.
>
>A developer at my client site is going to work on this problem today, using a couple of API calls into the MFC layer that handles memory management. Also, I've posed a similar question to someone at MicroQuill, about the possibility of using their product in VFP. I hope to hear from them very soon.
>
>The work I spent this weekend proves to me that I need to manage the memory usage in my application better than how it is being managed currently. I can't get through a day's work without having the app crash several times. Admittedly ,it is a complex application -- it has taken over a year to write, and does the job of several full-time clerical staff. But right now the staff could beat me in a race if I have to reboot the application every so often. :-)
>
>Any other thoughts, anyone?
>
>Ed

Strike one: The HeapCompact API call is not supported in Windows 95. Chad was able to find the heap(s) that the application is using, but when he called HeapCompact, it generated a 120 error.

I have a similar question I'm going to pose in a separate thread. It has to do with objects not destroying properly when a form is closed.

Ed