>Of course, this may happen always, but since superclass sometimes does work (I haven't paid much attention to the circumstances), I'm not sure.

I agree, superclass seems to have a mind of it's own when working with MMF stuff. One problem you always hit is if you try to use it on a bizobj that's been dropped on a form. Since the frameworks requires you change the name of a bizobj after dropping it (i.e - rename from MyBizObj1 to MyBizObj), that name change seems to confuse the heck out of superclass and it doesnt know how to trace up the inheritance change. I sometimes change the name back temporarily if I absolutely must get to higher code in form's bizobj... but in reality you should be doing you bizobj coding in the class designer for just that bizobj class (not in class designer for the form you dropped the bizobj on) Superclass always works fine there.

Another problem that can trip superclass is when vcx based classes get stuck in memory. Like if you cancel out of running the app, dont do a clear all and jump right into class designer then try to view method code higher up with superclas when the code you wanna see is stuck in memory. It gets confused, you need to close out of class designer, clear all, jump back in.

Plus too if you see superclass hanging out when your not modifying a classib, good sign it's already confused and you need a clear and or the occaisional close toolbar and relaunch fromt standard menu. HTH