A
amynard
Office 2007 (Beta2) products appear to have inconsistent behaviour when
opening "corrupt" files. By "corrupt", I mean where the zipped contents has
been manipulated by, for example, removing the "[Content_Types].xml" file
from the archive. If the office file has a correct extension, such as .docx
or .docm, then the file will be reported as corrut and will not be opened.
However, if you rename the file to have some other extension and then use
"Open with...", the file is reported as corrupt and will then be repaired and
opened.
This inconsistent behaviour does not seem sensible.
A particular example of where this applies is when a document has VB macros
in them. The expected behaviour is that if the file does not have a .docm
extension and does not have the correct entries in the "[Content_Types].xml"
file then the macros cannot be enabled. However by giving the file some other
extension and then using "Open with..." then macros can be used.
opening "corrupt" files. By "corrupt", I mean where the zipped contents has
been manipulated by, for example, removing the "[Content_Types].xml" file
from the archive. If the office file has a correct extension, such as .docx
or .docm, then the file will be reported as corrut and will not be opened.
However, if you rename the file to have some other extension and then use
"Open with...", the file is reported as corrupt and will then be repaired and
opened.
This inconsistent behaviour does not seem sensible.
A particular example of where this applies is when a document has VB macros
in them. The expected behaviour is that if the file does not have a .docm
extension and does not have the correct entries in the "[Content_Types].xml"
file then the macros cannot be enabled. However by giving the file some other
extension and then using "Open with..." then macros can be used.