K
Kim Finleyson
Has anyone experienced errors with Word merges after applying Service Pack 3
for Word 2002? If so, is there a work-around?
I work for a software company that programmatically opens MS Word and merges
data extracted from our application's database into a pre-existing Word
template that contains mail merge fields. After applying Word 2002 SP3, our
customers are receiving errors such as: "The document 'template.dot' caused
a serious error the last time it was opened...," "the action cannot be
completed because the other program is busy," and "Microsoft Word has
encountered a problem and needs to close." Our Support technicians advised
customers to change Macro security levels to low, trust all installed
add-ins and templates, and trust access to Visual Basic Project, but this
did not correct the problem -- it seems only upgrading to Word 2003 and
saving the document templates in 2003 corrects the problem.
I checked Microsoft's knowledge base and saw there were some security
measures applied to macros in RTF files with SP3, so could this be the
source of the problem? If so, is there anyway to programmatically bypass the
new security settings in Word 2002 SP3 in order to alleviate having to save
document templates with Word 2003?
Many thanks!
for Word 2002? If so, is there a work-around?
I work for a software company that programmatically opens MS Word and merges
data extracted from our application's database into a pre-existing Word
template that contains mail merge fields. After applying Word 2002 SP3, our
customers are receiving errors such as: "The document 'template.dot' caused
a serious error the last time it was opened...," "the action cannot be
completed because the other program is busy," and "Microsoft Word has
encountered a problem and needs to close." Our Support technicians advised
customers to change Macro security levels to low, trust all installed
add-ins and templates, and trust access to Visual Basic Project, but this
did not correct the problem -- it seems only upgrading to Word 2003 and
saving the document templates in 2003 corrects the problem.
I checked Microsoft's knowledge base and saw there were some security
measures applied to macros in RTF files with SP3, so could this be the
source of the problem? If so, is there anyway to programmatically bypass the
new security settings in Word 2002 SP3 in order to alleviate having to save
document templates with Word 2003?
Many thanks!