Hi,

I've just (after two days !) tracked down a bug in an application so I'm off to celebrate - but I'm wondering why it took so long. Background:

This is a VFP application that used a VB6 OCX control which, in turn, relied mainly on API calls for printing. We found that on extremely long print runs (or multiple runs without the application being closed) that VFP would hang. So the syptoms pointed to a memory leak but I couldn't find any evidence of such using the performance monitor. I eventually tracked down the initial error point to a PrintEnhMetaFile() and then to a failure to delete a windows Region object in the same VB function.

So my question is: Where, in this situation, is memory allocated for the Region object and how should I have been able to detect the resource leak?(I'll probably work it out for myself on Monday but pub beckons....)

Regards,
Viv