Word 2003 - set compatability option

[Guest]

Does anyone know how to set Compatability to Recommended options for Word
2003, when opening any existing documents? By code rather than manually.

Also similarly for unchecking the "Disable features introduced after Word
97" box?

Thanks

 

[Graham Mayor]

I am not sure why this should be necessary. Word will open older documents
without such juggling, however the following macro saved in normal.dot
should do the trick:

Sub AutoOpen()
Options.DisableFeaturesbyDefault = False 'Disable features introduced after
Word 97
With ActiveDocument
.Compatibility(wdNoTabHangIndent) = False
.Compatibility(wdNoSpaceRaiseLower) = False
.Compatibility(wdPrintColBlack) = False
.Compatibility(wdWrapTrailSpaces) = False
.Compatibility(wdNoColumnBalance) = False
.Compatibility(wdConvMailMergeEsc) = False
.Compatibility(wdSuppressSpBfAfterPgBrk) = False
.Compatibility(wdSuppressTopSpacing) = False
.Compatibility(wdOrigWordTableRules) = False
.Compatibility(wdTransparentMetafiles) = False
.Compatibility(wdShowBreaksInFrames) = False
.Compatibility(wdSwapBordersFacingPages) = False
.Compatibility(wdLeaveBackslashAlone) = True
.Compatibility(wdExpandShiftReturn) = True
.Compatibility(wdDontULTrailSpace) = True
.Compatibility(wdDontBalanceSingleByteDoubleByteWidth) = True
.Compatibility(wdSuppressTopSpacingMac5) = False
.Compatibility(wdSpacingInWholePoints) = False
.Compatibility(wdPrintBodyTextBeforeHeader) = False
.Compatibility(wdNoLeading) = False
.Compatibility(wdNoSpaceForUL) = True
.Compatibility(wdMWSmallCaps) = False
.Compatibility(wdNoExtraLineSpacing) = False
.Compatibility(wdTruncateFontHeight) = False
.Compatibility(wdUsePrinterMetrics) = False
.Compatibility(wdSubFontBySize) = False
.Compatibility(wdWW6BorderRules) = False
.Compatibility(wdExactOnTop) = False
.Compatibility(wdSuppressBottomSpacing) = False
.Compatibility(wdWPSpaceWidth) = False
.Compatibility(wdWPJustification) = False
.Compatibility(wdLineWrapLikeWord6) = False
.Compatibility(wdShapeLayoutLikeWW8) = False
.Compatibility(wdFootnoteLayoutLikeWW8) = False
.Compatibility(wdDontUseHTMLParagraphAutoSpacing) = False
.Compatibility(wdDontAdjustLineHeightInTable) = True
.Compatibility(wdForgetLastTabAlignment) = False
.Compatibility(wdAutospaceLikeWW7) = False
.Compatibility(wdAlignTablesRowByRow) = False
.Compatibility(wdLayoutRawTableWidth) = False
.Compatibility(wdLayoutTableRowsApart) = False
.Compatibility(wdUseWord97LineBreakingRules) = False
.Compatibility(wdDontBreakWrappedTables) = False
.Compatibility(wdDontSnapTextToGridInTableWithObjects) = False
.Compatibility(wdSelectFieldWithFirstOrLastCharacter) = False
.Compatibility(wdApplyBreakingRules) = False
.Compatibility(wdDontWrapTextWithPunctuation) = False
.Compatibility(wdDontUseAsianBreakRulesInGrid) = False
.Compatibility(wdUseWord2002TableStyleRules) = False
.Compatibility(wdGrowAutofit) = False
End With
End Sub


--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP

My web site www.gmayor.com

<>>< ><<> ><<> <>>< ><<> <>>< <>><<>

 

[Mastra]

Excuse me, but I have a compatibility problem.
I'm running Word 2003 SP3 and, when I try to open a document created with
Word for Windows 2.0, I receive the error "You are attempting to open a file
that was created in an earlier version of Microsoft Office. This file type is
blocked from opening in this version by your policy setting."
All my collegues with the same Word version have the same problem, while
people with Word 2003 SP2 can open the same document without any problem.
Is this an issue related to SP3?
Thank you.

Regards,
Massimo

 

[garfield-n-odie [MVP]]

It is poor netiquette to hijack someone else's question for your
unrelated problem. You should have posted a new question of your own.

Yes, this is the result of a security update in SP3 for Office 2003.
See http://support.microsoft.com/?kbid=922849 "You receive an error
message when you try to open or to save a file type that was blocked by
your registry policy settings in Word 2007 or in Word 2003".

 

[Mastra]

I'm terribly sorry.
I usually post in discussion groups and I know well the policies.
I didn't read well the first question - well, I only knew it was related to
compatibility - and I thought my problem could be related to it.
My fault.

Thank you very much for your reply.

Best regards,
Massimo Stramesi