Richard does a good job of explaining the basics of a concept in his videos. It's been very useful for me as I've worked for the past two years to create a shell for Access that is based on a rapid development system I started some 40 years ago.

Here's my take for developers on how to use the ideas appropriately.

I've now got hundreds of procedures in my shell application, Most are over 30 lines of code and have become complex because of layers of error checking that is needed between procedures as they communicate. There are only five or six procedures that are less than a dozen lines of code.

I like Tempvars, especially during development because of the persistence of values. When developing I'm getting constant RTEs that destroy variables when reset. So, I've got about two dozen Tempvars that get used a lot. That way I don't have to go back and start from login every time I crash.

Being able to test in the line of code without calling procedures over and over again hopefully speeds up the application. Whether to use a Tempvars or a procedure depends on factors such as location in code, frequency of use, possible future enhancements, complexity, etc. all things that require a bit of thought by the developer.