Jeff,

Does the section of code contain calls to getpem() and/or pemstatus()? Sometimes VFP will create internal object references that you have no control over, but there are workarounds to avoid these.

My tool from the library will only find "normal" object references that you are assigning in code. If you have an example like this that my tool can't find I'd appreciate seeing it so the tool can be refined.

>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.