Access OOP examples wanted

Here is a link that has some "oop" features to get current subform container name. Thanks to Markk and stopher; and IvanM for posing the question.
 
Last edited:
Here is a more recent youtube video dealing with class modules. It is by Steve Bishop (Programming) who has a number of vba related videos. He discusses an approach and the logic to validate data entered into textboxes on a form and creates class modules step by step to do that validation. It is the context and thought processes for needing/creating/coding and testing the class modules that I found helpful.

It references the RubberDuckvba vbe addin but it is the class module coding/usage that is demonstrated clearly for the viewer.


Also: Intro guide to class modules can be found here
 
Last edited:
While I am thinking about it, I'm attaching a ZIP file containing a polymorphism demo I threw together for a coworker. (It's a ZIP file because uploads of the basic accdb file are failing for some reason.)

Classes are intimately bound up in polymorphism, so this seemed the appropriate place to put the file.
 

Attachments

On a whim, I consulted my Access VBA Inside and Out book (Andrew Couch) regarding Class Modules. Some very good examples as well as detailed instructions on what they do and how to design them.

Where his book falls short however is how to determine when to use them. Fortunately, the article that JDraw shared bridges that gap.

I would share some of that code here but it be a direct violation to the terms on purchasing the book.

I will try to wrap my feeble brain around this...
 
I would like to see a video(s) (youtube/screencast???) to take a problem/opportunity from start to finish describing the business issue; recognizing a 'business object'; deciding/rationalizing the use of a class approach; developing the class with clear dialog and code;... This could be a series possibly. (very beginner ...additional complexity)

NG,
I think this could be a random topic/issue and use an approach similar to a book example without "infringing/violating" purchasing terms. I note that Frothingslosh said he uses classes regularly, so he may have more insight on how to bring classes to more vba developers/users.

Most of what I've seen or read indicates it's a mindset change, but once you "get it" you'll use classes more often.
 
jdraw said:
Most of what I've seen or read indicates it's a mindset change, but once you "get it" you'll use classes more often.
Click to expand...

AC said almost the exact same thing at the end of the chapter:
"Some might argue that rather than using classes, which involves constructing a framework, you could more simply have built a re-useable library. This line of argument nearly always holds; thus, the decision to use classes becomes a question of whether it seems more intuitive and natural than using a traditional code module."
Click to expand...

And at the very beginning before he proceeds:
"Many Microsoft Access developers take a look at classes and then give up because they have difficulty seeing the benefit and justification for using classes. It’s true that much of what can be achieved with a simple class can also be achieved by using libraries of code, and that to build classes you often need to put in more effort during the initial development, but there are benefits in using classes that will be explored in this chapter..."
Click to expand...

I suppose if I made a living developing applications for clients, this would be a handy tool to have. As it is, I only maintain one as a collateral to my primary purpose which is logistics planning.

All that aside, the ability to create a custom class of objects that can be used throughout your application - more specifically, having Intellisense provide you your objects as you code - is just plain NEAT.

My biggest hurdle at this point is to see how I can fit this in so that I can convince myself that the "juice" is worth the "squeeze".
 
Well, keep in mind that most of the stuff we work with in VBA are actually classes - every form object, every table object, DoCmd; they're all classes with properties and methods that we use.

Basically, when I'm writing code for my projects, I ask 'Is this a 'thing' or part of a related group of functions, or is this just a simple function?'. A function that simply, say, accesses the GetUserName function from the Windows API will remain a standalone function, whereas a series of functions that loads a recordset, validates the data, exports the data to Excel, and then formats the data will probably wind up bundled together in a single class. Same thing with user data - if your interaction with user data is a simple "are they allowed in yes/no" deal, then a stand-alone function is fine, but if you need to confirm access, pull their real name, save their permissions, save their email address, and deal with special access 'flags', and you need to keep referring to it throughout the use of the app, then a class is the way to go.

You may have seen that god-awful 'Importing data from Excel' procedure I posted in the repository a few years ago. A much more modern (and much faster) version of it I wrote at my previous employer (where I once again ran into the SAME FREAKING PROBLEM THAT SPAWNED IT IN THE FIRST PLACE :mad: ) uses classes and collections instead of arrays, largely because despite being a hair slower, they're MUCH easier for your successors to understand.

Seriously, though, the trick to the right mindset is just learning to look at something and realize that it's either a 'thing' you'll be dealing with a lot or doing a lot of complicated work with, or a collection of related stuff that really should be just bundled together (which is, honestly, what DoCmd is).
 
Last edited:
And honestly, classes stopped being intimidating once I just bit the bullet and wrote a couple. Beginners should just get a quick reference (I think Chip Pearson had a good one) showing how to set up properties and the Initialize and Terminate procedures, and then just write a couple and work with them.

I have simple examples in my Polymorphism example above, and my progress meters post over in the Repository is completely class-based.
 
NauticalGent said:
AND...I picked up a neat little trick on how to comment out a whole block of code in instead of "tip-toeing through the tulips"!
Click to expand...

I'f love to know about that, as I frequently comment out code when trying new things.
 
Wow, that is so handy, and it has been there all the time? :(

Thanks for that.
 
Gasman said:
Wow, that is so handy, and it has been there all the time? :(
Click to expand...

Yep. I always assumed everyone already knew about it.

Just as an FYI, if you use SQL Server Management Studio, it has the same buttons available there, too.
 
Tony,

It's funny you mention the wiseowl tutorial. I've seen many of these on classes and web scraping and find them excellent --although geared to Excel, but all done using vba. And easily portable to Access. There are several videos, all available free from wiseowl site. (see post #20 in this thread)

There are also some great youtube videos by Paul Kelly (Excel Macro Mastery) --collections etc.
He offers free webinars a couple of times a week (latest is http://excelmacromastery.us10.list-...ddd2e9d6edafa28440&id=02c97b38b4&e=d2b706b539 ). He is selling ( at a discount to webinar viewers) an Excel application product (http://excelmacromastery.us10.list-...ddd2e9d6edafa28440&id=0e427be75f&e=d2b706b539) for those interested. It is a handbook with 10 full blown vba applications. I'm not an excel person, but find his presentations quite well done and informative.

jack
 
Last edited:
Uncle Gizmo said:
Object-Oriented Programming is Bad
Click to expand...

Interesting take on OOP. I have lived some of his views while trying to tame the monster I inherited. I found myself rocking back and forth on simple issues as far as where to put the code (should I make a separate Module, should I put it in the Objects Class, do I make a "Utilities" Module, etc) instead of simply "just doing it". His metaphor about individually wrapped candies was spot-on!

All that being said, the true nature of this video really doesn't apply to most of us on this forum. A huge percentage of our coding is done within forms and reports which forces us to comply with OOP to some extent.

To a non-programmer such as myself, Access's code-behind-the-forms paradigm was a God-send. All of a sudden I could do cool things without having to take a butt-ton of CS courses and invest in pocket protectors.

Funny thing is, my first introduction to databases was with Paradox/PAL, which at the time was a break from traditional programming (or so I was told) but to really do anything spectacular with it, you had to write whole procedures.

When Windows 95 became the norm and subsequently MS Office, I rebeled against the machine and went an RDBMS strike until I was forced back into it in 2008. By then Paradox and all other RDBMS apps were marginalized and Access stood alone at the top.

I held my nose and started to learn it and after awhile I decided it didn't really smell all that bad and when Access became the reason for my employment a year ago, it smells 'purt damn nice.

Anyway, now that I have made this all about me, thanks for the video. It is refreshing to see different POV's on things.

Edit: On reflection, unless I missed something, the speaker never really spoke to the actual performance of OOP in relation to the other methods. Only the readability and other aesthetics. Hardly a solid platform to sell your case on...
 
Last edited:
I would like to know more of OOP. I was used to procedural programming during my younger years :banghead::o.

I have seen some of Uncle Gizmo's video and they're very good.
 
a sample User class

As per a conversation with John (Nautical Gent) in a thread about global variables, here is a basic User class that you might implement or customize or whatever. Your data access doesn't have to be as complicated as that cDataRecord class I use in there, but that's just my stock data access class so I'll leave it in. Note that this is just the User and doesn't have a related table/class for logins and logouts, which would make a ton of sense to add, but maybe this gives some idea of how to get started.

To make this work, double click the fUser form. Your Windows username will not likely be present in the table, so a Wizard will pop up right away to help you add yourself.

After that, opening the fUser form will automatically recognize your Windows login, and load your record from the table into a new instance of the class. You can also spoof other users by making a selection in the combo.

Makes sense?
Mark
 

Attachments

You must log in or register to reply here.

Similar threads

MajP
Form Instance Example
Replies
2
Views
185
MajP
MajP
MajP
Using A Collection Class to Raise Common Event
2
Replies
32
Views
2,577
MajP
MajP
D
Solved Disable Multiple Record Selection On Subform
Replies
7
Views
439
dalski
D
S
OOP in Access Applications
2
Replies
21
Views
2,595
isladogs
isladogs
lodmark
Solved Sorting with DISTINCT
Replies
19
Views
1,136
lodmark
lodmark

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top Bottom