E
EagleOne
2003, 2007
I believe I have the s/w but not the process to get my VBA into a DLL file
I now have C++ and have successfully compiled some Math-example program written in C++ into a DLL
which can be called by VBA in Excel. So far so good!
What is missing is what I want to accomplish - which is to protect my current VBA code.
What steps do I have to take to be able to drop my VBA (Excel) code into a C++ via Win32 Console
Application Project and then ending up with an Com Addin of a DLL?
As I see it there must be a way to get my VBA into C++ to end up with a DLL:
Plan A Plan B
1) have VBA code (Excel) 1) VBA code
2) Possibly save that code as a .xla file? 2) Drop into VB.NET and/or C++
3) Compile into DLL? (With what? and how?) 3) Compile into a DLL
4) Call new DLL from Excel VBA 4) Call DLL new from Excel VBA
I have a LInk to Chip Pearson's site and his information is excellent. That said, where does my
current VBA code get into the mix?
Any Thoughts appreciated!
EagleOne
I believe I have the s/w but not the process to get my VBA into a DLL file
I now have C++ and have successfully compiled some Math-example program written in C++ into a DLL
which can be called by VBA in Excel. So far so good!
What is missing is what I want to accomplish - which is to protect my current VBA code.
What steps do I have to take to be able to drop my VBA (Excel) code into a C++ via Win32 Console
Application Project and then ending up with an Com Addin of a DLL?
As I see it there must be a way to get my VBA into C++ to end up with a DLL:
Plan A Plan B
1) have VBA code (Excel) 1) VBA code
2) Possibly save that code as a .xla file? 2) Drop into VB.NET and/or C++
3) Compile into DLL? (With what? and how?) 3) Compile into a DLL
4) Call new DLL from Excel VBA 4) Call DLL new from Excel VBA
I have a LInk to Chip Pearson's site and his information is excellent. That said, where does my
current VBA code get into the mix?
Any Thoughts appreciated!
EagleOne