>Stacy,
>
>Your otherwise can be empty, a NODEFAULT followed by a DoDefault() does nothing to alter the default behavior. Try dumping the otherwise all together.

I had thought that NODEFAULT followed by DODEFAULT() was not always the same as putting no code in a method. The documentation I read said that Dodefault() executes code from the class from which the object was instantatiated, whereas NODEFAULT will suppress code from all levels -- including default base class behavior. So if you have an object well down in a hiearchy the combo would execute code from the immediate class, while the NODEFAULT would suppress code from all class above. This is not a correction, you are probably right, and I'm probably misremembering. I'm just asking this so I can get rid of a possible instance of "knowing somthing that's not so" the most dangerous type of mistake.