VBAPackager VS VBA-Project-Information

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 :)

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.