Home Creators Posts Import Register Favorites Logout

Downloads

Content

In this week’s Feature, Fix, or Focus, we take last week’s VBA Code Automator training.

Here's the list of updates I made for this training:

· Backup Workbook Macro requested by CCZ

· Autohotkey Overview requested by @tungsonnguyen7988

· Added 30 Additional Macros added by Randy Austin

· Added 25 VBA Scripts added by Randy Austin

Please don’t forget to add your requests for your own Feature, Fix or Focus each week when I post a new video, right here on Patreon. Each week I will either add a new feature, fix a bug or an issue, or create another training with a special focus on any part, all based on your feedback and comments.

Files

Comments

Gerrie Pretorius

Hi Randy, the script file is not included in the support file sections

Excel For Freelancers

Hi Gerrie, thank you for notifying me about it. I already uploaded the file in the post, please feel free to download it. Thanks again.

Ákos Szilágyi

Hi Randy, thank you again all of the great work and effort. I hope, write to this topic is not too late. The automator is awesome, I followed the coding with you. My problem is, when I try to add for example a "<" to one of the code, the autohotkey just get the code write back totally messed up. I tried the replace method ("<" -> {<}) but it couldn't do the trick. I try it with an advance filter exactly with a line "If LastResultRow < 3 Then Exit Sub". I can just assume that the problem is the "<". If you have any tips on this, that would be more than helpful! :D Thank you in advance for your opinion

Excel For Freelancers

Hi Akos, thanks for your comment and question. I ran some test in my Autohotkey (version 1) in which I did not find any issues with the < character. It seemed to be saved and returned as intended and saved as intended. There may be another cause or try Version 1 of Autohotkey to see if that makes any difference (it shouldn't though)

Jan Bolhuis

Hi Randy, I wanted to reach out to you regarding version 2 of the software. Before today, I hadn't utilized the #If WinActive function, but your comment in this video brought it to my attention as some shortcuts are only necessary in specific programs. Today, I revisited that part and discovered that your code didn't work for me because you are working in version 1 (this is just an assumption). However, I am determined to find a solution. I discovered that in version 2, #If is replaced by #HotIf. I wanted to share this information in the hopes of helping others who may encounter the same issue. I have included an example of one of my scripts below: #HotIf WinActive("ahk_class wndclass_desked_gsk") ; ensures following scripts run in the VBA Editor ::txtt:: { send("TextBoxTest") send("{left, 1}") } #HotIf PS: Thank you so much for all the great work you do and the knowledge you share. Cheers, Jan

Excel For Freelancers

That is great Jan, Did you test this in Version 1 as well? I will update my script as well and check. Thanks so much for your follow up on this. Much appreicated

Jan Bolhuis

Hi Randy, I just checked my script of version 2 in version 1.37.02. It came with an error. Did you get the same? Error at line 1. This script requires AutoHotkey v2.0. Current interpreter: AutoHotkey v1.1.37.02 Unicode 64-bit C:\Program Files\AutoHotkey\v1.1.37.02\AutoHotkeyU64.exe The program will exit.

Excel For Freelancers

Hi and thanks. Yes i saw that it had an error in V2. I still prefer version 1 and I am not sure why they needed to make such drastic changes so that the scripts are not interchangeable . So I will stick with version 1 for now as it works seamless with the VBA Automator. I will make sure to mention that during my videos as well. Thanks again