>>Just to elaborate, i'm setting .obelong to null in the objects destory method. If I try to do it in the form destroy I also get a fatal error.
>ie this.ade.obelong=null generates a fatal error.
>ade is the name of my object which is links to the list box
>
>I got mixed up. I thought the .oBelong property was a property of the Form, which is why I mentioned Form.Destroy(). I just wanted to make sure that the object that you referenced in that property did not attempt to get destroyed before the object with the property (or before that property was set to NULL), otherwise, the referenced object wouldn't get released/destroyed and chaos could result < g >.
>
>Hope you get it solved. I gotta go, and I'm outta town for a few days.
>
>Best...
>
>--Brad

OK, thanks Brad, you're probably gone.
I believe what is happening is that the list box is getting destroyed before the linking object. (I didn't think that should happen). Then when the linking object gets destroyed the .oBelong property is pointing to a non-existant thing. So C000005 when I set it to null or try to create it again in the same program session.

I can work around by using a temporary link only in the linking objects init event.