7
747733
I've been struggling with several problems since upgrading to Office
Professional 2003 SP2, on five computers. I have a Visual Basic application,
built with version 5.0 SP3, that runs on these five computers. This VBA ran
seemlessly with Office Professional 97 and 2000.
On two of the five computers, when I ran the VBA for the first time I
received a warning that macros were not signed. I went through the steps to
add the VBA as a "Trusted Publisher".
On the other three computers the VBA was already listed as a "Prior Trusted
Publisher". On these three computers I have tried, unsucessfully, to change
the "Prior Trusted Publisher" to "Trusted Publisher". I've tried every
possible combination of macro security between Word and Excel, but this
continues to cause problems.
During a mail merge process between Word and Excel (copy several Excel
charts and paste into text boxes in Word), if Excel's macro security is set
to anything other than low, I get the macro security warning and must
manually choose to "enable macros", at least 5 times during each step. And
Word crashes every time, no matter what its macro security is set at. I've
sent the Word error to Microsoft, electronically, several times. Microsoft
returns the following generic message for Event ID 1000:
We're sorry
There is no additional information about this issue in the Error and Event
Log Messages or Knowledge Base databases at this time. You can use the links
in the Support area to determine whether any additional information might be
available elsewhere.
Also during a mail merge process I have a problem with special characters.
In the text document that contains the tab delimited data, the special
character is correct (Chávez 85%). When it's merged into the Word document
it's converted to Chez 85% (the accented "a" becomes a box and the "v" is
gone).
If you can offer any advice, it would be greatly appreciated. I'm running
out of patience.
Professional 2003 SP2, on five computers. I have a Visual Basic application,
built with version 5.0 SP3, that runs on these five computers. This VBA ran
seemlessly with Office Professional 97 and 2000.
On two of the five computers, when I ran the VBA for the first time I
received a warning that macros were not signed. I went through the steps to
add the VBA as a "Trusted Publisher".
On the other three computers the VBA was already listed as a "Prior Trusted
Publisher". On these three computers I have tried, unsucessfully, to change
the "Prior Trusted Publisher" to "Trusted Publisher". I've tried every
possible combination of macro security between Word and Excel, but this
continues to cause problems.
During a mail merge process between Word and Excel (copy several Excel
charts and paste into text boxes in Word), if Excel's macro security is set
to anything other than low, I get the macro security warning and must
manually choose to "enable macros", at least 5 times during each step. And
Word crashes every time, no matter what its macro security is set at. I've
sent the Word error to Microsoft, electronically, several times. Microsoft
returns the following generic message for Event ID 1000:
We're sorry
There is no additional information about this issue in the Error and Event
Log Messages or Knowledge Base databases at this time. You can use the links
in the Support area to determine whether any additional information might be
available elsewhere.
Also during a mail merge process I have a problem with special characters.
In the text document that contains the tab delimited data, the special
character is correct (Chávez 85%). When it's merged into the Word document
it's converted to Chez 85% (the accented "a" becomes a box and the "v" is
gone).
If you can offer any advice, it would be greatly appreciated. I'm running
out of patience.