>What would happen if you put a statement like: > >This.oMyChildObject = .NULL. > >in the Destroy() event of the "parent" object and > >This.oMyParentObject = .NULL. > >in the Destroy() event of the "child" object? Those should both fire before >the Form is actually destroyed. Or even better, how about: > >WITH Thisform.txtOriginal >.oMyChildObject.oMyParentObject = .NULL. >.oMyChildObject = .NULL. >ENDWITH > >in the QueryUnload() or Release() methods? That would destroy those >references before the real objects ever got destroyed. > >By the way, why are you doing this particular textbox creation, anyway? >(backpedaling even further...) From the session I attended this afternoon, I asked the speaker about that situation, and I was told that most of this bug or "by design" thing has not been fixed. It seems that is something we need to take care of and what you described to putting .NULL. is the first thing to do. However, we need to add RELEASE This.oMyParentObject as well because .NULL. is not suffisant. We need to release the object from memory. Putting it in the Release() is the place to go.