Why not use a character depiction of the reference, instead of a direct pointer? This'll take a millisecond to resolve into a pointer when you require it, but it'll also allow you to blow away objects on a whim (or a crash) if required. In any of the application level classes that I use, I hold a character reference, just so I don't have a pointer holding the object open. > >If you are holding object references like this you are responsibile for > cleaning them up. One way to do this is to recurse through all of the > controls in the form iside the form's release and call a cleanup method > (that you created for teh contrl) that will .NULL. any object reference > properties before the normal action of the form's release tries to blow the > controls away. > > Jim, do you have any ideas about what to do when the form blows up and has > to be cancelled. THe usual cleanup code doesn't run, and I haven't figured > out how to get that reference out of memory. This has been an ongoing > problem during development, and even when I KNOW the object reference, I > can't set it to .NULL. from the command line.