NAMING OF A MODULE AND MAKING IT UNOBSERVABLE - VERY BASIC

[BEETAL]

sorry to be asking the very basic questions which the respected
participants(experts and novices)would find boring. I need help.

1. How to change the name from module1,module2 etc to desirednames in 2003
version.

2. can someone please give those few lines to make the modules unobservable.
I need to hide the codes.

 

[Jon Peltier]

1. Select the module in the project explorer window, then in the properties
window, change the name.

2. You cannot selectively protect just one module, you have protect the
entire project. Right click on the project in the project explorer, choose
XXX Properties, and fill out the items on the Protection tab.

- Jon

 

[BEETAL]

Sir,

Thanks for the help. BUT, I need to make the project Unobservable. Last time
some guy did hack into the password after running a software. I had a few
lines of code which made the project unobservable. The lines were in the
module itself. Obviously I cann't see them anymore.

The lines were again provided by an expert. Please try a little harder.
Thank you,Sir.

 

[Peter T]

Trying harder will not give you a better answer. There is no way to fully
secure your VBA code.

Whilst the project password will keep out most casual users if someone hacks
into your password your project and all its modules become viewable.
Only way to make your code more secure is with a different language, though
even most of these are not 100% secure except perhaps the closely related
VB(6)

Regards,
Peter T

 

[Barb Reinhardt]

Yes Mr. MVP Expert sir. Try a little harder. ::: ducking :::

I'm sorry I'm not going to be able to come to Atlantic City at the end of
the month. Maybe next year.

Barb Reinhardt

 

[Jon Peltier]

How much harder should I try? WOULD ALL CAPS BE HARDER?

You are claiming that the project was not visible in the VB editor? I have
not heard of such a thing, unless you are referring to a COM add-in, which
should be more uncrackable than VBA. At best, Excel and VBA security
provides an inconvenience to someone who really wants to see your code. It
would take me five minutes to find my notes on how to crack your code, and
probably 30 seconds to actually do it.

I don't do this, because most code isn't worth cracking.

- Jon