sancarn/awesome-vba

A curated list of awesome VBA/VB6 frameworks, libraries, software and resources

awesome-vba's Issues

Shall we credit directly?

E.G.

[🖼][p_win][⭐][a_all][🏺][o_32][👤](# "LaVolpe") [Universal DLL Calls](http://www.vbforums.com/showthread.php?781595-VB6-Call-Functions-By-Pointer-(Universall-DLL-Calls)) - A library which can be used to call functions of any function pointer, DLL or object in both `STDCALL` and `CDECL`. 

In ways I feel this would be a nice shout-out to authors of work?

But alternatively it could get political too... (Who was first? etc.)

TaskDialog 64bit

Very nice list, a lot of neat projects here I hadn't seen before.

Since you included one of mine, I thought I'd put in a note that you should remove the "32bit only" icon for TaskDialog, as I've now updated the VB6 project page to include the 1.3.8 Universal version, now that all features are available in VBA64 and I've updated the VB6 demo form to work with it. Project is also on GitHub now. The class works in VB6, VBA6, VBA7 32bit, VBA7 64bit, twinBASIC 32bit, and twinBASIC 64bit.

Excel Macro Mastery VBA articles in the Websites category

I see there is a link to the YouTube channel, but I think Paul Kelly's VBA Articles page also deserves a place in this list (the Websites category).

Libraries from leandroascierto.com

Hi @sancarn

You can add libraries coming from source:
https://leandroascierto.com/blog/

Includes many libraries for VB6 applications such as:

1. ucText
2. ucListView
3. ucVideo
4. ucCalender
5. ucMaps
6. ucGallery – Direct2D
7. ucJLDatePicker
8. ucListPlus
9. Class Shadow
10. Neumorphism Design
11. PopUp Menu
12. Custom Menu
    Thank you for sharing Awesome-VBA!

Suggest adding 🔗 emoji to document early-bound references?

I find myself avoiding early-bound references where possible, mainly because of their version instability. Is this something others would be interested in?

We'd be talking about references other than VBE7.dll, Excel.exe, stdole2.tlb, MSO.dll, FM20.dll ofc

E.G. If a library requires an early-bound reference to Scripting.Dictionary and VBScript.Regexp then we'd have the following:

* [🖼][p_win][⭐️][a_all][🔗](# "Scripting.Dictionary;VBScript.Regexp") SomeVBALibrary - Does something

However libraries which create Late-bound objects like:

set rx = CreateObject("VBScript.Regexp")

wouldn't have to include the emoji

Chilkat ActiveX Libraries

After reddit user techjp indicated that it might be awesome enough. As a result we added it to:

Frameworks:

* [🖼][p_win][⭐][a_all][💲](# "Some modules free; Some require $299+ license")[👽](# "Requires external dll") [Chilkat AXL](https://www.chilkatsoft.com/refdoc/activex.asp) - Numerous useful ActiveX libraries hosted from a single zip.

WebTools:

* From Frameworks
    * In `Chilkat AXL` find `HTTP`, `HTTPRequest`, `HTTPResponse`, `Auth*`, `OAuth*`, `REST`, `WebSocket` and numerous other useful web-related libraries.

This evening Kallum and I have been taking a look at it and we aren't certain it is awesome, so would like to put it to a vote. 5 votes and we will re-add it. I've added my vote to take into consideration techjps suggestion.

Reasons for removal:

The library does not follow any constructor naming conventions e.g. loadXYZ.

'Typical name convention
With new ChilkatCsv 
  .LoadFile(...)
End With

'Looks okay and expected
With ChilkatJson
  .LoadString(...)
End with

'would have prefered LoadFile... but ok
With new ChilkatXml
  .LoadXMLFile(...)   
End Wit

'Convention not followed
With new ChilkatGzip
  .ReadFile(...)
End With

'Convention not followed
With new ChilkatHttp
  .PostJson(...)
End With

It is important for a framework to remain internally consistent, as this will reduce the learning curve of the library. This is especially important when

Very few examples

Again difficult to learn what is correct to do without good and full examples.

Poor error checking(?)

In order to get a feeling for the library I tried to parse a csv and set the column "c" to the sum of "a" and "b". This code didn't error, but it didn't modify the csv either... I'm a little unsure whether I'm doing the right thing or not, but the lack of errors sure don't help.

Sub t()
  Dim x As New Chilkat_v9_5_0.ChilkatCsv
  Call x.LoadFile("C:\Users\sancarn\Desktop\tbd\chilkatax-9.5.0-x64\_test.csv")
  
  Dim i As Long: i = 1
  For i = 1 To x.NumRows
    Call x.SetCellByName(i, "c", x.GetCellByName(i, "a") + x.GetCellByName(i, "b"))
  Next
  
  Call x.SaveFile("C:\Users\sancarn\Desktop\tbd\chilkatax-9.5.0-x64\_test.csv")
End Sub

Missed sections in TOC

There are sections of the document that do not appear in the table of contents, such as the Parsers/Interpreters section that was available in earlier versions of Awesome-vba.

Section of office scripts for Office365?

Since Office365 web versions only support Office Scripts and since web-downloaded files do not execute macros by default, more and more people are trying to use Office Scripts for automations.

Are there any plans to add a section for these Office Scripts in the future?

VBA style guides

Removed both:

• todar's style guide - Has some decent basic guidance.
• VBA Standard - Guide prepared by moderators of the r/vba subreddit.

Currently these standards don't feel robust or thorough enough, and thus we don't feel they are "Awesome". Needs more work before adding to the list. See ruby style guide for an example of a full style guide.

Using images instead of emojis?

It seems to me that using images instead of emojis would be better for clarity, but I wanted to confirm if that's something you'd want to add (I don't know if the choice of using emojis was for simplicity or for aesthetic reasons).

Here's a proof of concept to see how it would look only for the Word Logo: https://github.com/DecimalTurn/awesome-vba/tree/6ae545daf684f0c42ee0b2cea4b6bf603f0348c0

Awesome list preperation

PR Requirements

PR Title: "Add VBA"
PR addition: "VBA/VB6 - Visual Basic for Applications (VBA) is an implementation of Microsoft's event-driven programming language Visual Basic 6.0 (VB6) built into most desktop Microsoft Office applications"

*Add to bottom of category, (not alphabetical order)

Author requirements

• Review open PRs (1) - sindresorhus/awesome#2541 (review)
• Review open PRs (2) -

Requirments

• Has been around for at least 30 days.
• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
• It's the result of hard work and the best I could possibly produce. If you have not put in considerable effort into your list, your pull request will be immediately closed.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
• The heading title of your list should be in title case format: # Awesome Name of List
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• [N/A] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file
• Includes a project logo/illustration whenever possible
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though
• Includes the Awesome badge
• Has a Table of Contents section
• Has an appropriate license >> (CC4)
• Has contribution guidelines >> (https://github.com/sancarn/awesome-vba/blob/main/Contributing.md)
• [N/A] All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents >> (Feel symbology needs to sit at the top as it's 100% required and needs to be known to understand the document)
• Has consistent formatting and proper spelling/grammar
• Doesn't use hard-wrapping
• Doesn't include a Travis badge; You can still use Travis for list linting, but the badge has no value in the readme.
• Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough

Tooltips on icons

I think it's quite cool you are building a list like this and BTW thanks for linking to one of my repositories.

I think it would be useful to have tooltips on top of the icons so that new visitors don't have to scroll up and see the meaning of icons in case they don't want to remember them.

For example instead of:
👑
you could use this:
[👑](# "Compatible on all platforms")
which looks like this:
👑

I think here it actually shows up as a link but in the main Readme.md it does not.

links to Ron de Bruin articles are obsolete

Ron de Bruin has decided to delete all of his Excel for Windows content, because part of it is outdated. Now, both links from this page are redirected to https://www.rondebruin.nl/history/ which explains the situation.

This is a shame if you ask me because a good portion is still very relevant and some of his examples are simply the best ones I ever found on some subjects (e.g. ribbon customization). But this decision was his to take, not mine.

I see three options :

• Link to archive.org (for the reason mentioned above, might not be a great experience people not used to it)
• Delete links (respect Ron's decision to delete content)
• Replace links to point to https://www.macexcel.com/, the other Ron de Bruin's website dedicated to Excel for Mac. There is less content and it focuses on Mac, but some info is also relevant on Windows