homerWS
asked on
VBA to DLL
Hello,
Is there any way to convert VBA to DLL quickly? Thanks in advance.
Is there any way to convert VBA to DLL quickly? Thanks in advance.
ASKER
Hi softplus,
The problem is that my VBA code is really huge. Its got 24 worksheets, 18 modules and 6 forms. Worksheets and forms has lesser codes, about 300 lines average. But 80% of the modules has about 4000 lines average.
Actually, with the DLL conversion, I am just trying to protect my codes from the user. Is there other way rather than DLL conversion? Thanks!
The problem is that my VBA code is really huge. Its got 24 worksheets, 18 modules and 6 forms. Worksheets and forms has lesser codes, about 300 lines average. But 80% of the modules has about 4000 lines average.
Actually, with the DLL conversion, I am just trying to protect my codes from the user. Is there other way rather than DLL conversion? Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi softplus,
I have tried coding in .NET but they are mighty slow. I thought maybe its my desktop but when I tried on the latest laptop my company gave me it was not that bad but was still slow compared to VB6. Therefore, I am still not impressed by it.
I haven't looked through the web pages, but I think I like the last paragraph about how you suggest tto convert some of the codes to the dll. I will look through the web pages and give yoy a shout back.
I have tried coding in .NET but they are mighty slow. I thought maybe its my desktop but when I tried on the latest laptop my company gave me it was not that bad but was still slow compared to VB6. Therefore, I am still not impressed by it.
I haven't looked through the web pages, but I think I like the last paragraph about how you suggest tto convert some of the codes to the dll. I will look through the web pages and give yoy a shout back.
Strange, I found .NET quite fast -- but of course it is a much larger overhead than VB6 so memory size makes a big difference (so it's not for every PC :)). Let me know if you need anything more :)
John
John
If you do not want the user to view the code, why not just put a password on the macro code?
How'd it go? :)
ASKER
dmang,
Password protecting the macro code is "hackable" using some sort of password recovery software. I have seen it done before.
Password protecting the macro code is "hackable" using some sort of password recovery software. I have seen it done before.
ASKER
Softplus,
Sorry for the late reply. Anyway, thanks for the tip.
Sorry for the late reply. Anyway, thanks for the tip.
True enough...
How desperate is your intended user group to see what's under the covers?
How desperate is your intended user group to see what's under the covers?
quickly: depends on how quick you can code :). You can't convert it 1:1, but most of the objects are available (indirectly at least) and the code is almost the same. Depending on the size of the VBA-Scripts it should be more or less a matter of copy + paste + cleanup afterwards. But: there are many things you can do much better in VB directly which could be re-coded to run cleaner / faster. If it's small, why not paste it into a 500'er question - I'm sure some of the experts would jump at it and do it for you :)
John