Hi Tom;

Exactly. At the risk of appearing dim-witted, I want to know how to write
the protection for Excel 2000 (and other versions if necessary)

I should be able to get the users version number through
'Application.Version' and if it's not 10.* (Excel 2002 --mine), I should be
able to write alternative protection code.

I have googled everywhere found lots of commentary and statements about
protection improvement in 2002 but no examples of how to deal with an earlier
version of Excel. Excel 2000 is probably all I need.

Regards Bill

"Tom Ogilvy" wrote:

First, officeXP is Excel 2002, not Excel 2003. Office 2003 contains Excel
2003

xl2000 has a different protection model than Excel 2002 (office XP) and
Excel 2003.

Not sure how protection is managed in your workbook, but it is possible your
problem is related to this.

--
Regards,
Tom Ogilvy



"Bill Case" wrote in message
...
Hi JLGWhiz;

"JLGWhiz" wrote:

Would they not have to run the macro again to reset the password when it
is
set by code? I am not sure how that works.

I am not sure how the whole password thing works in Excel. What I have
read
isn't more enlightening.

I use OfficeXP (i.e Excel 2003) my friend uses Excel 2000 as a stand
alone.
Every thing on my machine works as it is supposed to. Yes, password was
set
by the Worksheet.Protect properies. So, if it works for me, the same VBA
code should make it work for him. However, when he opens the workbook I
sent
to him or uses the Unhide macro I wrote, he gets an error message
generated
by On Error, and no password entry dialogue. The hidden columns Unhide
anyways.

"Bill Case" wrote:

What have I missed?

Regards Bill