Spellchecking template - receiving error message

[John Easley]

We are using a Word template to prepare formatted memos that are then emailed
to our users. I found an article at
http://word.mvps.org/FAQs/MacrosVBA/SpellcheckProtectDoc.htm, which contained
the code to unlock, spellcheck, and relock the template. It works very well
but only on workstations that are set up to allow the user Admin access.
Unfortunately, the vast majority of the workstations in our company are set
up to only grant User level access and the spellcheck function doesn't work
on those, even when we lowered the macro security level to Low. The security
policy cannot be changed to allow everyone Admin access.

Any suggestions to work around this problem and allow the spellcheck to run?
Any help will be appreciated.

Thanks,

John

 

[Jean-Guy Marcil]

We are using a Word template to prepare formatted memos that are then emailed
to our users. I found an article at
http://word.mvps.org/FAQs/MacrosVBA/SpellcheckProtectDoc.htm, which contained
the code to unlock, spellcheck, and relock the template. It works very well
but only on workstations that are set up to allow the user Admin access.
Unfortunately, the vast majority of the workstations in our company are set
up to only grant User level access and the spellcheck function doesn't work
on those, even when we lowered the macro security level to Low. The security
policy cannot be changed to allow everyone Admin access.

Any suggestions to work around this problem and allow the spellcheck to run?
Any help will be appreciated.

Just to clarify things...

Do you mean that users with User Access security level cannot use the Spell
Checking feature in Office products, ever?

If this is the case, talk to the IT people, they screwed up somewhere down
the line... I have never heard that spell checking availability had something
to do with PC security... The only way I see that there migth be a connection
is the custom dictionnary. It might be possible under some scenarios that
users with limited access not be allowed to create a custom dictionnary, but
spell checking itself should be available.

 

[John Easley]

Do you mean that users with User Access security level cannot use the Spell
Checking feature in Office products, ever?

I apologize for any confusion. Normal Spellcheck works fine for all of our
users. However, Spellcheck is disabled when the document is a protected,
locked template. Apparently, this is a known problem. The link I provided
above discusses it and provides the VBA code to automatically unlock the
document, spellcheck it, and relock it. This code runs fine on the
workstations that have admin access rights. It produces an error message on
any workstation that only has User-level access rights, which is most of
ours, even when the macro security level has been changed to Low. I'm
looking for a way around it so the code will run for anyone. Any help will
be appreciated.

John

 

[Jean-Guy Marcil]

I apologize for any confusion. Normal Spellcheck works fine for all of our
users. However, Spellcheck is disabled when the document is a protected,
locked template. Apparently, this is a known problem. The link I provided

According to MSFT, this is not a problem, it is by design!

above discusses it and provides the VBA code to automatically unlock the
document, spellcheck it, and relock it. This code runs fine on the
workstations that have admin access rights. It produces an error message on

At which point? Before the macro starts? During execution (which line of
code)?
What does the error message state exactly?

any workstation that only has User-level access rights, which is most of
ours, even when the macro security level has been changed to Low. I'm
looking for a way around it so the code will run for anyone. Any help will
be appreciated.

I have used that code before and I do not know of anything in that code that
would be influenced by user Access rights.

Have you checked if those users can run other macros? Even a simple one like
this:

Sub TestMe()

MsgBox "This is a test."

End Sub


How are you distributing the macro?
Word versions for all involved?

 

[John Easley]

Jean-Guy,

Thanks for your attempt to help. The problem seems to be resolved, now.
When I went in to gather the answers to your last questions, I exported the
module, deleted it from the document, and then reimported it. Now it is
working as expected. Not sure why or what exactly that changed but I'm not
going to argue.

Thanks again.

John