Larry,

Except that it's one of the blasted classes that can't be visually subclassed which means a SET PROCEDURE is involved which is nasty in itself. I'm just going to move the code a separate DefineXMLObject method and encapsulate it all there.

>What about subclassing it like Walter says and have a CLOSE ALL in the Destroy method? Is that quick and dirty enough?