Hello Mr. Lee:
I just read Amons's response to your question, and he is absolutely correct. The only thing I would add is that it is better to stay away from DODEFAULT() until M$ gets the bugs out of it. M$ has tried to fix it twice, and just managed to encode different bugs each time.
If you override a superclass method but still want to invoke the method of the superclass, use mySuperClass::myMethod() in your myClass.myMethod() code. Each time you create a new object of that class be sure to include a call to the superclass method for each method you override. This ensures that when you invoke the method in an object, all of the inherited code is called in an orderly fashion, step by setp, up the class hierarchy until the M$ base class is reached.
There is a bunch of information on using DODEFAULT() and NODEFAULT to invoke and avoid invoking superclass methods in the universal thread. Seach on the keywords DODEFAULT and NODEFAULT. There is also a little bit of information in the M$ knowledge base.
Regards,
JME
Jim Edgar
Jurix Data Corporation
jmedgar@yahoo.comNo trees were destroyed in sending this message. However, a large number of electrons were diverted from their ordinary activities and terribly inconvenienced.