Check that workbook that contains the module is active

[Jaymond Flurrie]

I'm working on my thesis and it makes a workbook to which it saves results to.

Once I have driven the code, I get those results and I go to check those and occasionally forget to activate the main workbook, even if I'm editing code in the main workbook's modules.

The question now is that how could I ensure that how my main workbook is active when I drive code from there? In some C# it would be something like "this.workbook.activate", but how does it go with VBA?

I change the name of my main workbook daily (so that I have some backups). That prevents from hard-coding the name of workbook to the code.

 

[mikerickson]

VBA has the command

ThisWorkbook.Activate

 

[RoryA]

You shouldn't need to activate workbooks. If your code creates the other workbook, then store a reference to that in a workbook variable. You can always refer to the workbook containing the code directly with ThisWorkbook as Mike said.

 

[Jaymond Flurrie]

VBA has the command

ThisWorkbook.Activate

Works great! Thank you.

 

[Jaymond Flurrie]

You shouldn't need to activate workbooks. If your code creates the other workbook, then store a reference to that in a workbook variable. You can always refer to the workbook containing the code directly with ThisWorkbook as Mike said.

I mean, the code drives itself thru perfectly, and after that I go to "manipulate" the results (or whatever playing around in the result workbook). Once my program is really finished, I'll make this so that my code is driven by pressing a button in a userform, that is located in that "code-workbook". Now when I drive the code directly from VBE, it's that kind of different, that nothing requires me to first click somewhere in the "code-workbook" and especially since I have two monitors, it's way too easy to forget to activate that "code-workbook".

But yes, you are right, I shouldn't need to activate workbooks once the code is finished. This is for testing purposes only.