Harold's comments need careful consideration in view of
the learning curve into vb and, from what I gather, some
4x longer to write and test.

But I'm with you, Mike, on this for all the reasons you
outlined. Slightly off topic but you mentioned copyright.
Unfortunately there's an enormous gulf between the
protection afforded in theory and what can in practice be
enforced. In rare examples if:
a) the issue is absolutely blatant,
b) you can identify the infringer,
c) you can demonstrate a material loss,
d) you have superior clout, financial or other (eg this ng)
e) he/she/entity has at least some decency
then you stand a chance. There's a successful illustration
here (you might spot a comment I threw in that
demonstrates my feelings on the subject):

http://tinyurl.com/6m839

Whatever, vba vs vb is the difference between putting up a
no entry sign and a small bolt on the door. But it's a
long trip to the hardware store to get this bolt!

Regards,
Peter


-----Original Message-----
you are all right. protection in this case isn't so much
for the code itself (indeed many samples of the code are
modified from that found here / google etc etc), but it is
more an attempt to protect the idea of how to reach an
end. At the end of the day, if someone wants at the code,
they will get at it whether it is encrypted etc or not...
if it is worth the effort. You can "copyright" code to a
point / code is intellectual property the moment it exists
with your name to it, but ideas cannot be protected...
and "method" doesn't usually apply to programming - but it
is this that sets one VBA project apart from another with
similar code snippets. A project that produces results
that are not achievable by any other means at the current
time is worth protecting - until alternatives are
developed... for once it would be nice if the "little guy"
could keep some control.

i really appreciate all of your comments & time. Many
many thanks.
.