stdVBA VS stdVBA-Compiler

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.

Long term, I have 2 projects VBA-Packager which attempts to do text->xlsm source injection, and VBA-Compiler which attempts to do vba-like --> vba compilation. The latter project of which is likely to be deprecated in a new project in the future. We'll see :)