Word 2007 variables error

[Peter Karlström]

Hi

We just discovered a very strange error in Word 2007, which we first thought
was our component VB6 COM-Addin, but after unloading it, the error keps occur.

We currently are running Office 2007 swedish with SP2 MSO (12.0.6425.1000)
We are testing the environment for an upcoming swith from compatibility mode
to
full Word 2007 dotc mode together with our COM Addin.

This is the steps to reproduce the error:

1. Start Word
2. Open VB Editor, and in the Immediate Window, type this:
activedocument.Variables.Add "testvariable", "testvalue" and press ENTER
3. Close VB Editor, close Word window and answer Yes to save the changes.
4. Save the file to Desktop
5. Open the file and switch tio VB Editor.
6. In the immediate window, type ? activedocument.variables("testvariable")
and press ENTER
7. The value is displayed but is corrupted.

If we check XML-code from the file Settings.xml in our testing environment,
many of the values we use gets the value w:docVa.

How come this is happening?

This is a very critical error for our system, since document variables holds
valuable pieces of information for handling the documents.

Hope anybody have som ideas.

Best Regards

 

[Tony Jollans]

There was a right royal mess made by Microsoft around SP2 with fixes for one
issue causing more serious issues. I forget all the details but there is a
hotfix
(http://support.microsoft.com/default.aspx?scid=kb;en-us;970942&sd=rss&spid=11377)
which will fix the underlying problem although, if you already have any
corrupted variables they have gone for good (unless you have your own
backups).

 

[Peter Karlström]

Thanks Tony

I will test this. Our issue is clearly mentioned in the article.

Again, thank you.

--
Peter Karlström
Midrange AB
Sweden

There was a right royal mess made by Microsoft around SP2 with fixes for one
issue causing more serious issues. I forget all the details but there is a
hotfix
(http://support.microsoft.com/default.aspx?scid=kb;en-us;970942&sd=rss&spid=11377)
which will fix the underlying problem although, if you already have any
corrupted variables they have gone for good (unless you have your own
backups).

 

[David Thielen]

There was a right royal mess made by Microsoft around SP2 with fixes for one
issue causing more serious issues. I forget all the details but there is a
hotfix
(http://support.microsoft.com/default.aspx?scid=kb;en-us;970942&sd=rss&spid=11377)
which will fix the underlying problem although, if you already have any
corrupted variables they have gone for good (unless you have your own
backups).

We hit the same thing and the hotfix does solve it. And yep - giatn
mess.

david@[email protected]
Windward Reports -- http://www.WindwardReports.com
me -- http://dave.thielen.com

Cubicle Wars - http://www.windwardreports.com/film.htm