Chris,

>Really? That's the same thing Alex was just asking. Happy joy...NOT. Might explain some of the problems I'm having then. Does calling MyChildObject.Destroy then set the MyObject.MyChild reference to NULL?

As long as it's successfuly, explicitly calling MyChildObject's Destroy() sets all references to it to .NULL.

>Strangely, I'm getting this behavior from the Grid Builder. I vaguely recall making some tweak that was supposed to deal with an undefined MM_Tempgrid error, but can't recall the details.

Sorry, doesn't sound familiar to me. Typically, the only MM builder I use is the one for creating data environments.

>More like naming my children rather than calling them child(1) and child(2).

Child1 and Child2 -- Dr. Seuss-ian, no? Is this the name of the "parent" propert(ies) in which you're storing the child reference(s)? If not, I'm thoroughly confused! Maybe a code example would help... How about one where the children are being stored (and named), and another one showing how you're attempting to reference them later?

>I'm changing the _access to use GetBizObject internally.

Sounds like a winner!

---J