Is there any utilities out there that will obfuscate the vba code?

What is the difference with com addin compared to a dll addin?

Which one of those can call a secondary addin?

Is there any limitations of moving the VBA code over to a addin?

Has anyone had exerience with Protection Plus?

I am planning on using many of these methods if they are feasible and
allowable by excel.

just starting with vba myself, but vba for dummies says
that the way to do that is by turning the code into an
addin which makes the code invisible to the user. The
book tells how to do this. further, the book says that
passwords are crackable - therefore offer little
protection.


-----Original Message-----
Is there any utilities out there that will obfuscate the
vba code?

What is the difference with com addin compared to a dll
addin?

Which one of those can call a secondary addin?

Is there any limitations of moving the VBA code over to a
addin?

Has anyone had exerience with Protection Plus?

I am planning on using many of these methods if they are
feasible and
allowable by excel.
.

No, addins don't make the code invisible, it makes the workbook invisible.

You can password protect the code, but that is not very secure.

Most secure way is to use a compiled process, like a dll.

--

HTH

RP
(remove nothere from the email address if mailing direct)


"Paul" wrote in message
...
just starting with vba myself, but vba for dummies says
that the way to do that is by turning the code into an
addin which makes the code invisible to the user. The
book tells how to do this. further, the book says that
passwords are crackable - therefore offer little
protection.


-----Original Message-----
Is there any utilities out there that will obfuscate the
vba code?

What is the difference with com addin compared to a dll
addin?

Which one of those can call a secondary addin?

Is there any limitations of moving the VBA code over to a
addin?

Has anyone had exerience with Protection Plus?

I am planning on using many of these methods if they are
feasible and
allowable by excel.
.

I understand that the password can be cracked easily. What Im looking to do
is make it more difficult. I have heard about obfuscating code, and , putting
majority of it in a com or dll. What Im looking for is any suggestions and
answers directly to the questions.

#1) Which is the perferable place to move code into a DLL or a COM addin?

#2) Can either of those call functions and procedures in another COM or DLL
file?
(Reason is I am considering using Protection Plus ) for trialware and
registration. I would like to place it into the DLL)

3) Limitations of moving code to DLL or COM?
(because I would like majority of the code moved ove, I need to no what
limitations are before I do this. And how different is VB from VBA)

4) Has anyone used Protection Plus by softkey. It is a Protection I hope to
use as part of the overall scheme.

5) does anyone know of any Obfuscating software that will make code
difficult for a person to decipher. I need this for VB and VBA.

I understand that the password can be cracked easily. What Im looking to do
is make it more difficult. I have heard about obfuscating code, and , putting
majority of it in a com or dll. What Im looking for is any suggestions and
answers directly to the questions.

#1) Which is the perferable place to move code into a DLL or a COM addin?

#2) Can either of those call functions and procedures in another COM or DLL
file?
(Reason is I am considering using Protection Plus ) for trialware and
registration. I would like to place it into the DLL)

3) Limitations of moving code to DLL or COM?
(because I would like majority of the code moved ove, I need to no what
limitations are before I do this. And how different is VB from VBA)

4) Has anyone used Protection Plus by softkey. It is a Protection I hope to
use as part of the overall scheme.

5) does anyone know of any Obfuscating software that will make code
difficult for a person to decipher. I need this for VB and VBA.





"Bob Phillips" wrote:

No, addins don't make the code invisible, it makes the workbook invisible.

You can password protect the code, but that is not very secure.

Most secure way is to use a compiled process, like a dll.

--

HTH

RP
(remove nothere from the email address if mailing direct)


"Paul" wrote in message
...
just starting with vba myself, but vba for dummies says
that the way to do that is by turning the code into an
addin which makes the code invisible to the user. The
book tells how to do this. further, the book says that
passwords are crackable - therefore offer little
protection.


-----Original Message-----
Is there any utilities out there that will obfuscate the
vba code?

What is the difference with com addin compared to a dll
addin?

Which one of those can call a secondary addin?

Is there any limitations of moving the VBA code over to a
addin?

Has anyone had exerience with Protection Plus?

I am planning on using many of these methods if they are
feasible and
allowable by excel.
.