ok, quick briefing on the Code Review Stack: you have code that works as intended, so you present it to reviewers in a "question" post where you describe what the code does, why it does it, etc.; basically you walk reviewers through it as you would one-on-one
and then reviewers "answer" with feedback on any/all aspects of the code
Mug WRT Document Modules. You could explain how to enable the VBIDE Extensibility (Tools>References>Microsoft Visual Basic for Applications Extensibility 5.3) object model. I had to think about this for a moment myself.
nah, it's because there was an incident a few years back around someone using profile pictures to do more or less evil things with, so people that don't have talk privs also don't get to have a fully visible chat account
This workbook
In the VBA project, the host document is referred to with an identifier, and that identifier is (by default anyway, and renaming it is not something Iād recommend doing) ThisWorkbook.
--> In the VBA project, the host document is referred to with an identifier, and that identifier is, by default anyway, ThisWorkbook (renaming it is not something Iād recommend).
@theVBE-it'srightforme I personally don't mind, because if worst comes to worst I have a few tricks up my sleeve to track down where I should know you from :)
that must be why I felt compelled to take German I back in college (dang that was already 20 years ago), ...I did score pretty well (~95%), but to a German native the class would probably have felt appropriate for 6yo kids
Accessing Worksheets
The magic Sheet1 identifier comes from the (Name) property of the Sheet1 document module under ThisWorkbook in the VBA project: set that property to a valid and meaningful name...
--> Instructions on how to do this really help inexperienced users.
Double click on the object in the Worksheet object in the Project Explorer to display the code behind.
In the menu at the top View>Properties Window (Hotkey: F4) to display the properties.
The first property (Name) at the top is the Worksheet.CodeName property. This is what you rename to a valid/meaningful name.
^ @MathieuGuindon Another one that I found to be large comprehension hurdle.
Wait, is it .Sheets() or .Worksheets()?
The first thing to note, is that they arenāt language-level keywords, but member calls. If you donāt qualify them, then in the ThisWorkbook module youāll be referring to Me.Worksheets (i.e. ThisWorkbook.Worksheets), and anywhere else in the VBA project that same code be implicitly referring to ActiveWorkbook.Worksheets: thatās why itās important to properly qualify member calls. Worksheets is a member of a Workbook object, so you explicitly qualify it with a Workbook object.
VBA Rubberducking
VBA Rubberducking