Re: Password protected document can't be merged

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Bob:

Quite correct, you can't merge to a document that can't be opened. So you
would have to specify the password.

But if you were using VBA, you could specify the password to open in the
code.

My point was that the new document created won't have a password -- you
would need to open each of the output documents individually following the
merge and set it.

Cheers


On 18/01/09 6:43 AM, in article C597B425.48FE5%onlygeneraltaz1@xxxxxxxxxxxx,
"Bob Jones" <onlygeneraltaz1@xxxxxxxxxxxx> wrote:

Hi John -

In order for the attachments to be created doesn't the original have to be
"opened" each time? If so it wouldn't be possible for the attachment to be
created since the doc couldn't be "read".

Regards |:>)
Bob Jones
[MVP] Office:Mac



On 1/17/09 5:08 AM, in article C597E437.1C49B%john@xxxxxxxxxxx, "John
McGhie" <john@xxxxxxxxxxx> wrote:

Hi Eddie:

Hmmm.... The document that is sent out from a mail merge is a NEW document
that is a copy of the Main Document. So the password is never going to
carry through.

She would have to write a macro to perform the mail merge, then individually
set the password on the resulting documents before emailing.

She should also understand that a password does NOT protect a document from
"editing" if the recipient is determined. If they can read it, they can
change it. There is no such thing as a document that "cannot be changed" by
a determined recipient who can read it.

She may be better off to simply ask the recipients "please do not change
this document". If they want to do the right thing, they will leave it
alone. If they are determined to do bad things, there is no format that
will prevent them doing so. It's the old story of "Locks only keep out
honest people".

What she COULD do (only on a PC...) is "Digitally Sign" the document. That
won't "prevent" changes, but it will instantly reveal the fact that the
document has been changed.

Hope this helps

On 17/01/09 4:02 AM, in article
21C8AE1D-2490-450C-BDD7-8E014B890E61@xxxxxxxxxxxxx, "Eddie"
<Eddie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hello all, I have a user that is trying to email merge a password protected
document to 69 recipients but can't. If she removes the password protection
she dosen't have a problem, but she needs the doc protected from any
editing.
Any suggestions on how she can accomplish sending out this document in a
protected format?

She is using office 2003

Thanks,
Eddie


--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Sydney, Australia. mailto:john@xxxxxxxxxxx

.

Relevant Pages

  • Re: Password protected document cant be merged
    ... She should also understand that a password does NOT protect a document from ... "editing" if the recipient is determined. ... but she needs the doc protected from any editing. ...
    (microsoft.public.mac.office.word)
  • Re: Password protected document cant be merged
    ... In order for the attachments to be created doesn't the original have to be ... She should also understand that a password does NOT protect a document from ... "editing" if the recipient is determined. ...
    (microsoft.public.mac.office.word)
  • Re: Send On Behalf Of
    ... > user did not have permission to send to this recipient. ... > specify a user in the From field. ... > Simple Mail Transfer Protocol (SMTP) virtual server. ...
    (microsoft.public.exchange.misc)
  • Re: can I set web.config to require authentication only for some files?
    ... If you have that many single pages to protect then you should consider ... you can indeed specify a directory to protect as a relative path in ... > one authentication method for one set of pages and a different ... >> You can specify some pages to require login, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: SPF = Sender Policy Framework
    ... > Now, to protect the privacy, this might mean, that every mail has ... want to change the way SMTP headers used in this way?" ... and so they're unable to filter based on the real recipient eMail ...
    (comp.os.linux.misc)