[AccessD] Example of Class Module usage needed

[Arthur Fuller]

Jim,

My first actual experience with O-O was Actor, which at the time was pretty
slick. I don't know whether it's still around either. Over the years I've
toyed with a bunch of various O-O languages, and become expert at none. But
it remains fun.

My thought on promotion applies to both attributes and methods, and by
extension to abstract classes as well. For example, if both class B and C
have an add method, which concatenates in class B and sums in class C, then
a promotion to the abstract class A would imply and demand an
implementation of add() in any descendant -- which in this case is trivial,
since both B and C already have the method. (This implies that in the GUI
there would be the usual difference between Drag-Drop and Drag-Copy;
perhaps the latter would want CTRL+Drag, or something.)

Do any of the O-O IDEs present a view of the hierarchy in a similar
graphical form as the one I'm suggesting?

A.
​