I have been looking to protect a rather large and useful VBA codebase from
prying eyes.

To date I have been using the standard Excel password protection but the
password crackers zap this in their sleep - only 1:10 secs was required on
an old P166 clunker!

What are the options to really secure the code? I have ruled out (for the
moment) porting it to C++ and then compiling it an .xla. Would porting to
VB provide equivalent protection? Or is there some clever VBA arrangments
that can be made?

Some other ideas I had are...
1. if I could strip (programagically) all the comments just before release
to make any crackers task more tedious,
2. perhaps hex edit the password hash to gobblegook so it can _never_ be
matched by the cracker - would a downside of this be that it stops the VBA
engine from firing?

Cheers, Frank.

You can't really protect it in VBA. You have to convert to compiled code (a
dll) with routines that are called by "wrapper" routines in the VBA project.


On Wed, 18 Aug 2004 09:41:54 +1000, "Frank_Hamersley"
wrote:

I have been looking to protect a rather large and useful VBA codebase from
prying eyes.

To date I have been using the standard Excel password protection but the
password crackers zap this in their sleep - only 1:10 secs was required on
an old P166 clunker!

What are the options to really secure the code? I have ruled out (for the
moment) porting it to C++ and then compiling it an .xla. Would porting to
VB provide equivalent protection? Or is there some clever VBA arrangments
that can be made?

Some other ideas I had are...
1. if I could strip (programagically) all the comments just before release
to make any crackers task more tedious,
2. perhaps hex edit the password hash to gobblegook so it can _never_ be
matched by the cracker - would a downside of this be that it stops the VBA
engine from firing?

Cheers, Frank.

"Frank_Hamersley" wrote in message
...
I have been looking to protect a rather large and useful VBA codebase from
prying eyes.

To date I have been using the standard Excel password protection but the
password crackers zap this in their sleep - only 1:10 secs was required on
an old P166 clunker!

What are the options to really secure the code? I have ruled out (for the
moment) porting it to C++ and then compiling it an .xla. Would porting to
VB provide equivalent protection? Or is there some clever VBA arrangments
that can be made?

Some other ideas I had are...
1. if I could strip (programagically) all the comments just before release
to make any crackers task more tedious,

Rob Bovey's Code Cleaner does this as I recall

2. perhaps hex edit the password hash to gobblegook so it can _never_ be
matched by the cracker - would a downside of this be that it stops the VBA
engine from firing?

Cheers, Frank.



Probably.

If you are using Excel 2000 or higher then consider moving the
code to a COM add-in in VB6

Much of the module code will be relatively easy to move but
the forms will need reddrawing and there are some subtle differences
between forms in VB6 and Userforms in VBA. For example listboxes
in VB dont support multiple columns

I just completed moving an application with 15 forms and
8 code modules , it took me approx 2 weeks.

http://msdn.microsoft.com/library/de...sLibraries.asp

Keith




----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! 100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---