2003, 2007


For whatever reason(s), getting information on this issue seems to be a real challenge.

After doing quite a bit of reading, it appears that one Must manually convert VBA to VB.NET (C++;C#)
to create a DLL or Com Addin?

Would someone please put me out of my misery? I keep hoping that there is a better way of
protecting VBA code.

At this point, I realize that procedures written in VBA and "compiled" with VB6 can make it to a DLL

But, since I do not have VB6, it appears that I can use C++, or C# or VB.NET to get the code to a
DLL - but I must translate each line of my VBA code to the respective alt language.

TIA EagleOne

(Any thoughts helpful - I HAVE SUCH A HEADACKE on this issue.)