Understanding Microsoft Access VBA Class Modules

Class modules can seem intimidating in Microsoft Access VBA, especially if most of your code lives in standard modules and form events. This episode explains what class modules actually are, how they differ from tables, forms, reports, and standard modules, and why they are not something every Access developer needs to use.

Learn the basic object-oriented ideas behind classes, including blueprints, objects, instances, properties, methods, encapsulation, and the difference between Property Get, Property Let, and Property Set. A simple employee class example shows how separate objects can each retain their own data and behavior.

We also cover when class modules can be useful, such as modeling customers, employees, invoices, shopping carts, or reusable form behavior. Just as importantly, we discuss when a plain standard module is the clearer and better choice. Classes are a useful advanced tool, but they do not replace good relational table design or make a database better simply because they sound fancy.