"In object-oriented programming, the term is used to describe a variable
that may refer to objects whose class is not known at compile time and which
respond at run time according to the actual class of the object to which
they refer. " (
http://wombat.doc.ic.ac.uk/foldoc/fo...gi?polymorphic)
Variables of type Access.Form are polymorphic: They may refer to any form
class, and respond at run-time according the actual class of the object to
which they refer. Variables of type Object are even more polymorphic: they
can refer to any object class.
The word polymorphic is derived from the idea 'many structures'. An Access
form can change structures: it may be in Form or Datasheet mode, so it is
polymorphic (bimorphic???) in a general sense. But since it is an Object,
not a Variable or Function, it would not, in it self, mean that Access or
VBA 'supported polymorphism'.
Changing the appearance and characteristics of an object is not the same as
changing the structure, so it would not generally be called polymorphism. In
fantasy terms, Shape-changing or death is morphing: changing the appearance
and characteristics is just Glamour.
(david)
"James Fortune" <ja******@oakland.edu> wrote in message
news:a6**************************@posting.google.c om...
In response to different users or situations (data context) I
transform the appearance and characteristics of Access Forms through
code. This seems to fit in with the idea of polymorphism. Do people
consider Access Forms to be Polymorphic?
James A. Fortune
