[AccessD] Access and OOP

[Arthur Fuller]

John,

Access is nof OOP. It is close but fails on a few significant aspects. I
cannot create a class and then inherit from it. I cannot do polymorphism
without a bunch of VBA code that points to the pseudo-class I created.
More to the point, OOP is pretty much a dying creed of code. Originally it
sounded like a great idea, then turned out to be a rhinocus with only two
feet -- in other words, a very awkward beast.
Initally I was seduced by the claims of Bertrand Meyer et. al., but that is
no longer the case. I still think in OOP, but Access is simply not an OOP
language. I would call it Not Oop, but kist an Object-Based Language. I
suppose this is merely a matter of terminology, but since you know more
than a little about VC and C++, you surely must understand the difference.

On Mon, Aug 31, 2020 at 7:53 AM John Colby <jwcolby at gmail.com> wrote:

> It is 2020.  OOP has been around for a long time and Access is, top to
> bottom oop.  So...
>
> If you were to interview with the mythical organization C2Db for an Access
> position, I would ask you:
> 1) Do you understand OOP?
> Yes.  The only acceptable answer in 2020.
> 2) What is a class? A code construct that allows you to model a real world
> object, storing code and variables (and events) for that object.
>
> --
> John W. Colby
> Colby Consulting
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur