>>Would that be RemoveObject first, then destroy? Does that safely get rid of everything so I don't have "dangling object references?"
>
>Cindy,
>
>You can call the destroy all day long and it won't do anything. Destroy does NOT destroy an object, it is an event that fires while the object is being destroyed. IOW, if an object gets destroyed its destroy event will fire. Calling a destroy event does NOT destroy the object, it just runs the code in the event.
>
>To get rid of the container call the RemoveObject of its parent container (in your case the Page).

Thanks for the good explanation, Jim. I'm still getting events and methods mixed up.

I wanted to be sure RemoveObject() completely removed the object from memory, but help just said that it "disappeard from the screen" and I had visions of it floating in limbo waiting to give me a C0x5 error. There isn't a RELEASE() method for the container like there is for a form.