Sunday, 12 March 2017

AET VBE Tools v1.7

Finally they're ready!

What's new?

1. Rename Userform Controls
This tool allows you to batch rename all controls on a userform via a simple Find and Replace interface. In addition to changing the control names, it also changes code with the old control name to the new control name.

So, if you want to change all controls that start with "CommandButton" to "btn" or "cb", etc, this is the way to do it all at the same time!



2. Make Project Variables List
The bigger the project, the more complex it becomes.

This tool analyses your code and makes a list of variables and constants.



Details include:
  • Module Name (Where the variable or constant is)
  • Scope (Public, Private, Type or Procedure)
  • Location (Declaration or procedure name)
  • Name (Variable or constant name)
  • Type (Variable or constant type, eg String, Long, etc)
  • Const (True or null, to discern between variables and constants)
  • Const Value (Value if constant)
  • Found in Project (Count within project)
  • Found in Report (Count within report)
  • Modules Count
  • Procedures Count
  • Unique Values
  • Duplicate Values

    More features are planned in the near future.

    3. Copy Code for Web
    If you need to show your code on the web, normal indenting won't show. The way to get around it is to convert indent spaces to " ".

    This tool does that and copies the code to the clipboard so you can paste it where required.

    4. Delete Orphan Code
    This feature was added at the request of Kellsens Willamos, who has supported me and the development of these tools from the beginning.

    What's "orphan code"?

    When developing, did you ever click userform controls by mistake? Maybe you get something like this.

    Private Sub lblSelectProject_Click()

    End Sub


    Chances are you don't want the code, and if there's nothing between the first and last line, it's a fair bet that you don't. The Delete Orphan Code tool looks for code like this and gets rid of it.

    I've added it as an option on Cleanup Project Code. To include it, tick the checkbox on the Settings form.



    AET VBE Tools are no longer free. But I'm keeping the price low so they are affordable. (And you will get future versions free of charge!)

    You can download them here.

    P.S. Tick the G+1 icon at the bottom of my post to tell me if you like what you see!

  • Monday, 6 March 2017

    AET VBE Tools v1.6.4 and Overall Progress

    Latest patch - 2 bugs have been fixed, and one change has been made to certain wording.

  • Fixed an indentation bug when the first procedure of a module was at the very top (No Option Explicit and no Declarations).

  • Also fixed a bug with Macro Comment Tools when more than one tool was used with the form still open.

    And I changed the wording of some messages to simplify translations for international versions!

    2 translations are being prepared - Portuguese and Japanese - and I want your help to translate into other languages!

    Please contact me the email address below.



    Other Progress
    It's been a super busy week getting the tools ready for translations, but there's more good news!

    I've started work on a version that works with Microsoft Word and plan to make a version for other Office products.

    Will keep you updated!

    For now, download AET VBE Tools v1.6.4 here.

    Ticking the G+1 icon at the bottom of my posts fuels my enthusiasm!

  • Tuesday, 28 February 2017

    AET VBE Tools v1.6.3

    This patch concerns another change to the Undo code, and is in case you unchecked "Trust access to the VBA project object model" after launching Excel. Perhaps unlikely, but I like to avoid potential bugs whenever possible.

    v1.6.3 is available here.

    Also, thanks to everybody who ticks the G+1 icon at the bottom of my posts. It gives me incentive to keep doing my best!

    Sunday, 26 February 2017

    AET VBE Tools v1.6.2

    Just a quick post to let you know the a new patch has been uploaded.

  • Indentation had a bug fixed when there were comments immediately after "Then" in If... Then code.

  • Cleanup Project Code had a minor tweak to alert you when no options were chosen.

  • I disabled Undo when a different tool is run.

    Undo should be used (if you wish to) immediately after you use a tool. So having it still enabled after using another tool may have caused confusion.

    Many thanks to those who have helped me improve these tools. Your support is appreciated!

    I'm happy to say the next version is already finished with 3 new tools, I'm just waiting for the online store to get things set up. Hoping for early March at this stage.

    Until then, v1.6.2 is available here.

    Update: I just released patch v1.6.3 that has another improvement to the Undo code.

    If you like my tools, please click the G+1 icon on this post and/or my blog's sidebar to let me know ;-)

  • Saturday, 18 February 2017

    AET VBE Tools v1.6.1

    Yes, it's still freeware. Think of it as a patch.

    I'm still committed to updating this version by fixing any bugs that I find, or tweaking this and that with improvements. It won't have as many features as upcoming versions, but I don't intend to abandon it either.

    So, what's new?

  • An indenting bug was fixed for Select Case constructs when working with Projects and Modules.


  • I also improved the indenting of Add Line Numbers code.


  • When adding the date and time to text files being exported, the code has been adjusted to show the correct time.


  • I made a change to the Copy Code and Compare Code userforms. Sometimes duplicate file names were showing.


  • I edited Highlight Code In Excel so that individual Case statements are also highlighted with Select Case constructs.


  • Case Statements

    Note: It is a big help to see them highlighted this way. Unfortunately I had to hard code that part, so it will only work if your tab settings are set to 4. (In the VBE, Tools, Options, Editor, Tab Width). If I find a way to determine this programatically, I will adjust the code to suit.

  • As a small bonus, I also added the functionality to delete Debug.Assert and Stop to the Cleanup Project code.




  • Download it here.