Separate the code from the data. Every professional developer from the
one-person shop to the largest software company in the world does that.

To get started, see http://groups-
beta.google.com/group/microsoft.public.excel.programming/msg/7fcd7a49ca
8efc52?
safe=off&as_umsgid=MPG.185a8ddd52ccd5ce98a88c@msne ws.microsoft.com&lr=&
num=100&hl=en


--
Regards,

Tushar Mehta
www.tushar-mehta.com
Excel, PowerPoint, and VBA add-ins, tutorials
Custom MS Office productivity solutions

In article ,
says...


"Jim Cone" wrote:

Mail them a CD via the Postal Service.
Media rates are very reasonable.

And how do you get end-user supplied data from the old sheet to the new one?
Copy it all over, in a macro of course, but for all intensive purposes, by
hand... since you have to program the macro to do the copying. So instead of
just changing your VB code, you have to change your VB code AND write a
function to copy end-user supplied data from the old workbook to the new one,
not only once, but many times over if the location of that data changes.

Is that time investment really THAT worth it?

I can't be the only one that thinks the esiest solution would be to allow
VBProject.unprotect , but then simply have a checkbox in the same Dialog box
as your VBProject protection information that dissalows VBProject.unprotect
from executing, thus negating and "brute force" attacks that cannot already
occur with SendKeys?


-or-
Supply the password to the user.


Whats the point of passwording a sheet so the end user cannot make changes
(integrity of your formulae) only to supply that same user the password?
Jim Cone
San Francisco, USA