Jeff,

Are you using VFP 6.0 and, if so, have you applied SP3?

It has a few fixes for "memory leak"s. One of them refers to PEMSTATUS. Now I don't remember details on what might be another bug with PEMSTATUS (ie may not be the memory leak), but it was something along the lines of two or more PEMSTATUSes in a row or on the same line caused a problem.

As for finding dangling references, have you tried David F.'s File #9466 - ObjRef-finds dangling references in the files section here.

Good luck,

Jim N

>Is there any good strategy for debugging dangling object references that keep a form from releasing properly? I've identified the portion of code that, if run, produces the behavior, but I cannot identify any object references left danging by the code.
>
>I am not sure which object refs are holding the form, which is part of the difficulty in debugging.
>
>Surely there must be some way... AMEMBERS() and DISPLAY OBJECTS show nothing.
>
>Help!
>
>-- jas