Hi Richard, With the help of Microsoft Copilot, I've been making a workflow database with class modules. It has an interface class, a concrete class for each state (or status), a context class, and a state factory class. I like it because the logic for each state is stored in its own class and the permissions are checked in the context. So it's very organized. But for someone who's never done any object oriented programming, it seems pretty complicated. Just wondering if this is the way you'd go about making your security seminar database with class modules or if there's a simpler way? thanks, Robert
I'm very upfront about this whenever I talk about class modules. In my 20+ year consulting career, I almost never needed class modules to get a database project done. They're powerful and you can do some really cool things with them, but they're absolutely optional in Access.
For most Access applications, including what I teach in the security seminar, a simpler, more procedural approach is usually easier to build, understand, and maintain. If you're comfortable with object-oriented design and enjoy that style, great. If not, you're not doing anything "wrong" by skipping it.
Robert BragaOP
@Reply 9 months ago
Hi Richard,
Thanks for getting back to me. I just have one more question for you. You mentioned in one of the classes that you didn't really need to use classes because you're a diciplined developer. Could you explain what you mean by that? What things do you do or don't do that make you a diciplined developer? Thanks. Looking forward to more developer classes on classes.
Sorry, only students may add comments.
Click here for more
information on how you can set up an account.
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.
This thread is now CLOSED. If you wish to comment, start a NEW discussion in
Access Developer 51.