Password error from Word2003 to Word2007

Hi Tony,

I would be interested to know what benefit Microsoft get for making this
such a complex procedure - not just the e-mail, but the frequently changing
password as well. I know you can't answer, I'm just musing
It was the first attempt to introduce a changing password. And that
was such a great idea that they added this feature to Word and even
improved it: a password that changes immediately...

Being awestruck,
Lorenz

LOL!

--
Enjoy,
Tony

www.WordArticles.com

"Lorenz Hölscher" wrote in message
...
Hi Tony,

I would be interested to know what benefit Microsoft get for making this
such a complex procedure - not just the e-mail, but the frequently
changing
password as well. I know you can't answer, I'm just musing
It was the first attempt to introduce a changing password. And that
was such a great idea that they added this feature to Word and even
improved it: a password that changes immediately...

Being awestruck,
Lorenz

It is ActiveDocument.Variables. In my tests they were destroyed on saving
the document - after I had added new ones (that is, both the ones I had
added and existing ones I hadn't changed). I haven't done extensive tests, I
figured any level of data destruction is intolerable.

I haven't looked at Document Properties - I daren't!!

--
Enjoy,
Tony

www.WordArticles.com

"Lorenz Hölscher" wrote in message
...
Hi Tony,

Tony Jollans schrieb:
I have done some testing on this and it does appear that the hotfix is
causing the destruction of document variables. I will raise the issue
with
Microsoft and report back when I have more information.
is it ActiveDocument.Variables or
ActiveDocument.CustomDocumentProperties? Are they being destroyed by
saving the document or do I have to delete one to destroy the others?

Regards, Lorenz

Hi Tony,

Tony Jollans schrieb:
It is ActiveDocument.Variables. In my tests they were destroyed on saving
the document - after I had added new ones (that is, both the ones I had
added and existing ones I hadn't changed). I haven't done extensive tests, I
figured any level of data destruction is intolerable.

I haven't looked at Document Properties - I daren't!!
The CustomDocumentProperties did survive, but you're right: any data
destruction is intolerable. And unfortunately we use the variables in
our code.

It's your turn again, Microsoft!

Regards, Lorenz

Hi Tony,

Tony Jollans schrieb:
I have done some testing on this and it does appear that the hotfix is
causing the destruction of document variables. I will raise the issue with
Microsoft and report back when I have more information.

did you succeed in discussing the issue with MS? "My" company needs to
solve this problem (no more form field documents world-wide for them!)
and will escalate the problem to MS. Is there something like a ticket
number or a we-know-the-problem-and-are-thinking-about-it-message or
even an announcement of a second hotfix?

Thanks,
Lorenz

Hi Lorenz,

I raised both the original password issue, and the hotfix variable issue
separately on "Connect" (connect.microsoft.com). The IDs are 452381, and
458719, respectively; they say they are publicly viewable but whether that
really means public, or just MVPs, I'm not sure (I haven't really got to
grips with Connect yet). They promise to review issues within five working
days but have not yet responded to either, which is rather disappointing.

To my mind the second issue is by far the more serious in that it is 'silent
but deadly' (you get no indication it has happened until you've already lost
your data). Form protection passwords can be removed and nothing is lost,
and only a limited number of users are affected. I can only hope they are
working hard to solve this issue.

--
Enjoy,
Tony

www.WordArticles.com

"Lorenz Hölscher" wrote in message
...
Hi Tony,

Tony Jollans schrieb:
I have done some testing on this and it does appear that the hotfix is
causing the destruction of document variables. I will raise the issue
with
Microsoft and report back when I have more information.

did you succeed in discussing the issue with MS? "My" company needs to
solve this problem (no more form field documents world-wide for them!)
and will escalate the problem to MS. Is there something like a ticket
number or a we-know-the-problem-and-are-thinking-about-it-message or
even an announcement of a second hotfix?

Thanks,
Lorenz

Hi Tony,

we'll see what will happen (or will not).

Thanks, Lorenz

There is now a hotfix for the hotfix. Although I haven't personally tested
it, I am told it works. The description at
http://support.microsoft.com/kb/970942 does not mention the problem directly
but, nonetheless, it is the one.

--
Enjoy,
Tony

www.WordArticles.com

"Lorenz Hölscher" wrote in message
...
Hi Tony,

we'll see what will happen (or will not).

Thanks, Lorenz