>>>>>>Have you included memory management via SYS(3050) / SYS(1104)? Might you have a memory leak that's only manifesting itself after a very long period of time?
>>>>
>>>>Hey Al. Intersting idea. After each report is run, I will print SYS(1016) to see if the amount of memory is climbing.
>>>>
>>>>Just curious, what makes you think that this could be a memory issue? Clicking on the window shouldn't revive the app if it was memory problem, should it?
>>>
>>>Just a WAG, one of those things that may crop up when an app runs 24/7, even if the leak is only a few bytes per operation.
>>>
>>>IIRC there used to be a problem in earlier versions of VFP with REPORT (...PREVIEW?) leaking a file handle under some circumstances. It's these sorts of things that can creep up on you.
>>
>>Nothing concrete yet, but the evidence is pointing to your solution. As the days pass, the amount of memory used by the app is slowly growing. Not sure yet if it is a leak, or if I am not releasing something. Thanks for suggesting this.
>
>Do you think that sys(1016) is reliable? How exactly can I test if there is a memory leak?

I'm not sure if it is reliable. As my exe runs day, after week, after month the value/1024 reported grows upwards from 754. If the sys(1016) is reliable then it seems the memory requirements for the exe are growing and that that must be caused by a memory leak. If it isn't reliable then I know nothing. :-)