I have a situation where I've been using a report listener for a good while. It's from Cesar Chalom and it's been working fine. It's for adding watermarks to a report. The client wants to adjust the watermarks and so they sent me some new images. They also added an option of no watermark. I had to make some minor changes to the program to accomplish this and didn't think much of it. It would be hard to introduce a bug with the small changes I made. The program seems to run fine, but I noticed that if I try to compile it again after running it, it now says the EXE is still in memory and can't be released. Very true. CLEAR ALL, CLEAR MEMORY, RELEASE ALL and other such commands don't help. I have to quit VFP and restart it. It does seem to be only related to using the report listener. If I do everything like I'm going to print the report, but then don't, or if I choose the None option (the new "no watermark" option which does not employ the listener), the problem does not occur. But if I let a watermark print, which does use the listener, then I get the "EXE still in memory" problem when trying to compile the next time.

I tested for memory leaks using SYS(1011) on an older version of the app that does not exhibit this behavior and the new version that does:

Memory Handles     Old version   New version
After VFP starts:  2009          1899
After 1st run:     1802          1835
After 2nd run:     1804          1840
After 3rd run:     1806          1845
After 4th run:     1808          1850
After 5th run:     1810          1855

From this data, it appears the old version may have a memory leak, too, however it does not exhibit the new problem and seems to have had no problem in production. Does anyone have any thoughts on how to track this down?

Thanks,

Russell Campbell