Yeah, I get what you're saying, and sometimes when I watch YouTube tutorials, I'm kind of the same way. I'm like, just answer the question already (or even with articles). You see a clickbait title and you're like, "Okay," and then they have the whole ton of fluff and it's like, just get to it already." I get that, and I might, moving forward, try to focus on giving the short answer first and then the more detailed answer.

Half the time when I find a YouTube tutorial that I like (if I'm not watching it for entertainment purposes), if I'm watching it to learn something (like most tech stuff), I just grab the transcript and have ChatGPT summarize it for me instead of sitting there watching 20 minutes of fluff. And also because I find most YouTube tech tutorials to be unbearable to watch. Lots of smart people out there, but not a lot of people with good presentation skills. It's either one or the other: either they're entertaining and their material is garbage, or the material is interesting but I can't understand a word they're saying. Or they put me to sleep.

But I do get it, so I understand where guys like this are coming from. But I like to think that my explanations help to enrich the understanding of the answer. Right? It's like that one I just did about the fiscal sorting. If I just give you that formula up front, that really doesn't teach you anything. That's why I walked through the query example on how we do that and use either the IF or the CHOOSE function to move that quarter. It gives you a better understanding of why I do that and how that formula kind of works. So I don't know, maybe I'm just crazy. Maybe I don't know what I'm doing lol.

I agree lot of smart people out there butttt the presentation they do is something that needs a lot of work on.  And I understand what you are doing and prefer it except when I know 50% of it (Maybe) in which case fast forward or beg ChatGPT and then have to go back to your video and that part I ignored.

I think I just parrotted what you said.

Jeffrey patience is a virtue. And it has its own rewards.
When I started my journey with Richard's website, I jumped around a lot, fast-forwarded a lot, and got frustrated a lot.
Then, finally, Ifollowed his advice, and I watched every single training course on Access, Excel, Word, and PowerPoint in order. Then I watched every tech help video in chronological order. That is approaching 2000 videos.

Because of that, I went from being constantly lost and frustrated to becoming a moderator in less than a year and a half.

Richard, I absolutely love the way you present your tutorials don't change a thing. What I really love is to hear the audio of you reading that comment out loud to yourself  because in my head it might  sounded like $#@!%% (or at least thats what I might say , LOL!) As always keep up the amazing work.

Sami I'm guilty of jumping around from time to time myself. Finally I'm taking the lessons more or less in order. But then when Ricard fails to name some object I find a way to distract myself by thinking "Forget Adam yelling at you because you didn't change the object name because  I'm screaming thing as well". Evenbtually I have to rewatch part of it because of that distraction.

The other day was working on my own form. I placed a textbox on it and it said TextBox1701.  Do I change the name because the Trekie in me doesn't want to? Or do I follow Richards rule and wonders how the &^$% I got up to that many Textboxes in a single form in the first place? :D

1701 objects on a form? Damn. :)

There's that number and 2112. Whenever those show up "in the wild" I always have a chuckle. I pumped gas the other day and without trying, I looked up and it said $21.12. I was like "sweeeet!"

Jeffrey I know the feeling.
And btw, 1701 is not how many text boxes you have in that form, but how many controls, including the ones that you have deleted. On an empty form, you add:
- textbox1
- command2
-label3

Having said that, 1701 controls is a huge number.

Yeah, and every time you add a text box and you get a label with it, that counts as a control too.

I realize the error in my comment but 1701 would be tough one to rename.  The one thing I have been re-reminded of is wrting code in small batches and testing and debugging vs writing a ton of code and then having to debug a lot of code. So for that.... thanks Admiral Rost

Yep, instead of one big long subroutine, break it up into smaller ones. That's what I always do.

I am just starting to do that too.  Long ones are hard to follow.

That's what she said.

For me, the "how to do it" doesn't stick nearly as well unless I know why we do it that way, aka why it works.  By learning "why", I have been able to discover how to do other things that you haven't taught.  This allows me to organize my thoughts into a knowledge base from which I can recall and teach myself.  This has also been my experience in other areas of my career.  

For my kids, I use the analogy of organizing files into ordered folders in a cabinet vs throwing a bunch of random loose papers into the same cabinet.  I appreciate you teaching the "why "and tying the lessons back to the core mission of learning to manage my data.

I do love that analogy. In my Windows beginner level 1 class (yes, for the absolute noobs), I teach the analogy of the desktop having tons of pieces of paper all over them and that's your system memory. When you want to save those and get them out of the way so you can work on different stuff, you put them in the filing cabinet (which is your hard drive). Same principles, different stuff.