The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs:
Microsoft Office Excel 2007
Microsoft Excel 2010
Microsoft Excel 2013
Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.
Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.
<1> Section 2.2: This namespace was introduced in Excel 2013.
<2> Section 2.2: This namespace was introduced in Excel 2010.
<3> Section 2.2: This namespace was introduced in Excel 2010.
<4> Section 2.2: This namespace was introduced in Excel 2013.
<5> Section 2.2: This namespace was introduced in Excel 2013.
<6> Section 2.6.3: Office Excel 2007, Excel 2010, and Excel 2013 do not always write the correct value into this field (1). Although the value of this field (1) is validated on load, it is not used at run time.
<7> Section 2.6.3: Office Excel 2007, Excel 2010, and Excel 2013 do not always write the correct value into this field. Although the value of this field is validated on load, it is not used at run time.
<8> Section 2.6.10: The following table shows the different versions of function accuracy that Excel 2010 and Excel 2013 supports.
Value
Meaning
0
Functions are calculated using the current application’s algorithms.
1
Functions are calculated using algorithms implemented in Office Excel 2007.
2
Functions are calculated using algorithms implemented in Excel 2010.
<9> Section 2.6.24: Office Excel 2007 does not support multiple uses of the same OLAP measure in one cache hierarchy, and does not discard the associated cache hierarchy when ignore is TRUE.
<10> Section 2.6.25: Office Excel 2007 will not ignore the fldattribute of the ancestor CT_DataField ([ISO/IEC29500-4:2011] section A.2).
<11> Section 2.6.30: Office Excel 2007 does not ignore these complex types.
<12> Section 2.6.31: Office Excel 2007 does not support multiple uses of the same OLAP measure in one PivotTable view, and does not ignore this pivot field when ignore is TRUE.
<13> Section 2.6.34: The 2007 Office system does not load a file in which this field (1) contains a value that it does not recognize, or is not recognized by the underlying operating system. The 2007 Office system recognizes the following language tags.
<15> Section 2.6.48: Office Excel 2007 does not ignore the ancestor CT_CacheField element.
<16> Section 2.6.63: Excel 2010 and Excel 2013 requires that the corresponding ListItem ([ISO/IEC29500-4:2011] section 14.4.2.36) be present.
<17> Section 2.6.65: Excel 2010 loads and roundtrips this value for scroll bars and spin boxes, but it does not support its functionality.
<18> Section 2.6.65: Excel 2010 requires that the corresponding FmlaRange ([ISO/IEC29500-4:2011] section 14.4.2.29) be present.
<19> Section 2.6.65: Excel 2010 and Excel 2013 ignore this attribute. This attribute is being deprecated.
<20> Section 2.6.65: This attribute is being deprecated in Excel 2010. Its functionality will be replaced with attribute noThreeD.
<21> Section 2.6.65: Excel 2010 loads and roundtrips this value, but it only supports its functionality for scroll bar form controls when run in a dialog box .
<22> Section 2.6.65: Excel 2010 does not support this attribute.
<23> Section 2.6.65: Excel 2010 does not support this attribute.
<24> Section 2.7.16: Excel 2010 uses this value only when the drop-down control is run in a dialog box, in all other cases the drop-down control behaves as a standard combo box.
