>Sorry for the delay, I don't think I've got the hang of
>this UT thang yet.
>
>The final "CLEAR ALL" in the program releases this
>object (of course), and many of the (record image)
>objects hanging off it try to check for a record lock.
>This is in the destroy method of the (sub)objects,
>the reference to the top object fails, complaining
>that it doesn't exist!
>
>The object *must* exist, it's clearing down it's
>dependant objects.
>I wonder if the name of it has been hidden during
>this process tho'.
>
>It doesn't seem to make any difference whether this
>object is global or not.
>
>Enough extra?


Like I said in the other message that if you are using multiple Clear All's then thats your problem. Look at Help -- Clear all does just that!

Tom