OOP in Access Applications

[isladogs]

Macros are a thing ...

... and you did right to skip straight to VBA! (Don't bother with Access macros).

Agree but with two exceptions: Autoexec and Autokeys, both of which have functionality that isn't directly replicable from VBA

 

[SparklySpartan]

Autoexec and Autokeys both of which have functionality that isn't directly replicable from VBA

Very true, luckily I did learn those but nothing else. Well, I learned the absolute minimum to get them running VBA so I could ditch whatever other scratch-like language they were using

 

[SparklySpartan]

Access is a RAD tool and if you are going to use Access, you should use its RAD features which help you to avoid code

I think I see what you're saying. You can't exactly compare Access to other general purpose languages and environments. Access is more focused on a certain kind of application and comes with a lot of prebuilt components to help you quickly assemble that kind of application. It would be a shame to lose time making your own code all of the time when you could be taking advantage of these components and methods they already give you, because that's the strength of Access in the first place. Otherwise, you're just trying to use it like you'd use other tools that offer more full flexibility but make you write all those components yourself or grab some libraries from others, and you're bound to keep clashing against what Access is actually trying to be.

It's RAD, which is pretty rad as far as I'm concerned XD

 

[isladogs]

Very true, luckily I did learn those but nothing else. Well, I learned the absolute minimum to get them running VBA so I could ditch whatever other scratch-like language they were using

Macros use XML

 

[Uncle Gizmo]

I could ditch whatever other scratch-like language they were using

You can start out with macros and then convert them to VBA it's not a very clean process and there is a gotcha which you should be aware of !!

More information on my website here :-

TempVars Value Error - Nifty Access

You cannot Always omit “Value” I often see people are advised they do not need to refer to a Control's Value implicitly like this:- Dim strValue As String strValue = cboCurrent.Value This advice is given because "Value" is the default, therefore it is unnecessary to append it, So you could write...

niftyaccess.com

Extract :-
I discovered a minor issue when converting a Macro to VBA code. You may have to include the “Value” Property for your text box or combo box (whichever control the the macro is associated with) – this seems a bit odd to a seasoned Microsoft Access programmer because the value property is normally a default and you don’t have to add it

and here's the video :-

TempVars Value Error - Nifty Access​