VBA-Project-Information VS stdVBA

I understand that VBA may be intended to help with spreadsheet handling at its birth(probably) but everything you mentioned is quite right because I am in the middle of developing a choropleth map in Excel using msoFreeForm shapes and another project which walks through VBA code modules to provide insight into VBProject with code obfuscation and visual codeflow diagrams, I got myself overwhelmed time and again and had to restart from scratch a number of times already. But with each iteration came, the need to compartmentalize/modularize, as I began to understand the need to improve my coding style or else.

You could write your own obfuscator code. I'm writing one.

Hi, sancarn, just greeting! We talked about your VBA shape Events class some time ago, I was working on a shape map project back then. I hope you will probably remember me once you see the image of the map. Still haven't finished it yet as I was side-tracked to another project which walks through VBA project code modules.

I do RPA from VBA personally using IAccessiblity. See stdAcc (https://github.com/sancarn/stdVBA/blob/master/src/stdAcc.cls) and an example (https://github.com/sancarn/stdVBA-examples/tree/main/Example...)

You could have just treated everything as variant correct? That's what we do here: https://github.com/sancarn/stdVBA/blob/master/src/stdLambda....

The responses I got was a mix. Some businesses didn't take me seriously because the main language I used was VBA. Some businesses claimed I was too eager and I "didn't have a life". No one seemed to care about the achievements I had made in the languages, like building a DSL in VBA, or this electron app. I did eventually get a job in another engineering firm though, where I spend 90% of my time to this day programming.

Really depends what you actually want to do and how neat (or fast) you want your code to be too... I typically use stdEnumerator and stdLambda from stdVBA.

Sometimes, though more of a library / tool developer here. See stdVBA or stdVBA-examples

That said it is effort. After building stdLambda which brings lambda syntax to VBA, I can tell you that error handling in this class is still trash. It's just a lot of effort to write good error messages, and handle all errors correctly. Still definitely an item on the TODO list, but will it ever be a priority? idk

Otherwise this library poses as an example of how to use stdVBA libraries. Libraries used in this project: stdEnumerator, stdArray, stdCallback, stdCOM, stdICallable, stdLambda, stdRegex.

If you want a solution though see stdSettings. There are both system and user settings. Users are bound by their domain, so should work across organisations :)

Use stdVBA's stdAcc:

Explaining code in such a way that it codes the correct thing is pretty awful though... Let's try to do that for stdTimer.