# 5 Appendix A: Product Behavior

**Office**

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

Microsoft Excel 97

Microsoft Excel 2000

Microsoft Excel 2002

Microsoft Office Excel 2003

Microsoft Office Excel 2007

Microsoft Excel 2010

Microsoft Excel 2013

Microsoft Excel 2016

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates 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.1.7.15: Excel 2002, Office Excel 2003, Office Excel 2007, Excel 2010, and Excel 2013 can write, load, and process the Signatures Stream in a file. Excel 97, Excel 2000 can load a file with a Signatures Stream but ignores it.

<2>
Section 2.1.7.20.1: When saving unsupported **future records** (section
2.1.6), Excel 97, Excel
2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 will
write those records at the end of the **substream** (section 2.1.3) in which they were
encountered during load, in the order in which they were encountered.

<3>
Section 2.1.7.20.2: When saving unsupported **future records** (section
2.1.6), Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007,
Excel 2010, and Excel 2013 will write those records at the end of the **substream**
(section 2.1.3) in which they were encountered during load, in the order in
which they were encountered.

<4>
Section 2.1.7.20.2: If a **Continue** record (section 2.4.58) is needed in the **MSODRAWING**
rule (section 2.1.7.20.2),
Office Excel 2003, Office Excel 2007, Excel 2010, and Excel 2013 can write out
an **MsoDrawing** record (section 2.4.170) instead of the
first **Continue** record (section 2.4.58).

<5>
Section 2.1.7.20.3: When saving unsupported **future records** (section
2.1.6), Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007,
Excel 2010, and Excel 2013 will write those records at the end of the **substream**
(section 2.1.3) in which they were encountered during load, in the order in
which they were encountered.

<6>
Section 2.1.7.20.3: If a **Continue** record (section 2.4.58) is needed
in the **MSODRAWINGGROUP** rule, Office Excel 2003, Office Excel 2007, Excel
2010, and Excel 2013 can write out an **MsoDrawingGroup** record (section 2.4.171) instead of the
first **Continue** record (section 2.4.58).

<7>
Section 2.1.7.20.4: When saving unsupported **future records** (section
2.1.6), Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007,
and Excel 2010 will write those records at the end of the **substream**
(section 2.1.3) in which they were encountered during load, in the order in
which they were encountered.

<8>
Section 2.1.7.20.5: When saving unsupported **future records** (section
2.1.6), Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007,
and Excel 2010 will write those records at the end of the **substream**
(section 2.1.3) in which they were encountered during load, in the order in
which they were encountered.

<9>
Section 2.1.7.20.6: When saving unsupported **future records** (section
2.1.6), Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007,
Excel 2010, and Excel 2013 will write those records at the end of the **substream**
(section 2.1.3) in which they were encountered during load, in the order in
which they were encountered.

<10>
Section 2.1.7.20.6: Office Excel 2007, Excel 2010, and Excel 2013 can save
out a CELLTABLE without a **Row** record (section 2.4.221).

<11>
Section 2.1.7.20.6: If a **Continue** record (section 2.4.58) is needed
in the **MSODRAWING** rule (section 2.1.7.20.2), Office Excel 2003, Office
Excel 2007, Excel 2010, and Excel 2013 can write out an **MsoDrawing**
record (section 2.4.170) instead of the first **Continue** record.

<12>
Section 2.1.7.21: Only Office Excel 2007 and Excel 2010 can write the **XML
Signatures storage**. Only Office Excel 2007 and Excel 2010 can load and
process a file with a **XML Signatures storage**; Excel 97, Excel 2000,
Excel 2002, Office Excel 2003 can load a file with a **XML Signatures storage**
but ignore it.

<13> Section 2.2.3.11: Graph Component for Excel 97, Graph Component for Excel 2000, Graph Component for Excel 2002, Graph Component for Office Excel 2003, Graph Component for Office Excel 2007, and Graph Component for Excel 2010 can create files that do not conform to these rules.

<14> Section 2.2.3.11: Graph Component for Excel 97, Graph Component for Excel 2000, Graph Component for Excel 2002, Graph Component for Office Excel 2003, Graph Component for Office Excel 2007, and Graph Component for Excel 2010 can create files that do not conform to these rules.

<15> Section 2.2.3.11: Graph Component for Excel 97, Graph Component for Excel 2000, Graph Component for Excel 2002, Graph Component for Office Excel 2003, Graph Component for Office Excel 2007, and Graph Component for Excel 2010 can create files that do not conform to these rules.

<16> Section 2.2.3.11: Graph Component for Excel 97, Graph Component for Excel 2000, Graph Component for Excel 2002, Graph Component for Office Excel 2003, Graph Component for Office Excel 2007, and Graph Component for Excel 2010 can create files that do not conform to these rules.

<17> Section 2.2.3.11: Graph Component for Excel 97, Graph Component for Excel 2000, Graph Component for Excel 2002, Graph Component for Office Excel 2003, Graph Component for Office Excel 2007, and Graph Component for Excel 2010 can create files that do not conform to these rules.

<18> Section 2.2.4.3: Office Excel 2007 and Excel 2010 save metadata records when cells contain formulas referencing cube functions. However, this metadata does not remain associated with the cells and is only recorded for the purpose of load and calculation optimization.

<19> Section 2.2.9: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 warn the user when they enter passwords that contain characters other than alphanumeric characters or punctuation symbols.

<20> Section 2.2.10: In Excel 97, Excel 2000, Excel 2002, and Office Excel 2003 the maximum password length is 15 characters. In Office Excel 2007 and Excel 2010 the maximum password length is 255 characters.

<21> Section 2.2.10: Only Excel 2002 and Office Excel 2003 will save files with XOR obfuscation.

<22> Section 2.2.10: Only Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 will load and save files with RC4 CryptoAPI encryption.

<23> Section 2.4.3: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 write a value for this field but ignore it on load.

<24> Section 2.4.3: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 write a value for this field but ignore it on load.

<25>
Section 2.4.9: When the base unit is not days, and the data is near the
base value of the date
system specified by the **Date1904 record** (section 2.4.77), **catMin**
value can underflow and get saved as a large number.

<26>
Section 2.4.9: When the base unit is not days, and the data is near the
maximum value of the date system specified by the **Date1904 record**
(section 2.4.77), **catMax** value can overflow and get saved as a small
number.

<27>
Section 2.4.21: Excel 97 writes 0x07CC for **rupYear**.

<28> Section 2.4.21: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, Excel 2010, and Excel 2013 set the value to 0 on creation, and change it to 1 in subsequent loading and saving.

<29> Section 2.4.21: This happens only for Excel 97.

<30> Section 2.4.21: Excel 97.

<31> Section 2.4.21: Excel 2000.

<32> Section 2.4.21: Excel 2002.

<33> Section 2.4.21: Office Excel 2003.

<34> Section 2.4.21: Office Excel 2007.

<35> Section 2.4.21: Excel 2010

<36> Section 2.4.21: Excel 2013

<37> Section 2.4.21: Excel 97.

<38> Section 2.4.21: Excel 2000.

<39> Section 2.4.21: Excel 2002.

<40> Section 2.4.21: Office Excel 2003.

<41> Section 2.4.21: Office Excel 2007.

<42> Section 2.4.21: Excel 2010.

<43> Section 2.4.21: Excel 2013

<44> Section 2.4.22: Office Excel 2003, Office Excel 2007, and Excel 2010 will prompt the user in this case.

<45> Section 2.4.22: This behavior does not apply to Office Excel 2007 and Excel 2010.

<46> Section 2.4.30: Specifies either Excel 97, Excel 2000, Excel 2002, or Office Excel 2003.

<47> Section 2.4.30: Specifies either Office Excel 2007 or Excel 2010.

<48> Section 2.4.45: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 save negative values, but at load time the negative values are corrected to 0.

<49> Section 2.4.45: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 save negative values, but at load time the negative values are corrected to 0.

<50> Section 2.4.45: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 save negative values, but at load time the negative values are corrected to 0.

<51> Section 2.4.45: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 save negative values, but at load time the negative values are corrected to 0.

<52> Section 2.4.46: Office Excel 2007 and Excel 2010 can save values greater than or equal to 0 and less than or equal to 200. In Office Excel 2007 and Excel 2010 the view angle is determined by dividing this value by a factor of 2.

<53> Section 2.4.46: Office Excel 2007 and Excel 2010 can save values less than 5.

<54> Section 2.4.46: Office Excel 2007 and Excel 2010 can save values greater than 500.

<55> Section 2.4.46: Office Excel 2007 and Excel 2010 ignores this bit and will set it back to zero if the file is resaved.

<56> Section 2.4.49: Excel 2000

<57> Section 2.4.49: Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, Excel 2010, or Excel 2013

<58> Section 2.4.49: Office Excel 2007

<59> Section 2.4.49: Excel 97

<60> Section 2.4.49: Excel 97

<61> Section 2.4.49: Excel 2000

<62> Section 2.4.49: Excel 2002, Office Excel 2003

<63> Section 2.4.49: Office Excel 2007

<64> Section 2.4.49: Excel 2010

<65> Section 2.4.49: Excel 2013

<66> Section 2.4.49: Excel 2000

<67> Section 2.4.49: Excel 2002, Office Excel 2003

<68> Section 2.4.49: Office Excel 2007

<69> Section 2.4.49: Excel 2010

<70> Section 2.4.49: Excel 2013

<71> Section 2.4.54: Specifies Office Excel 2007, or Excel 2010.

<72> Section 2.4.54: Specifies Office Excel 2003, Excel 2002, Excel 2000, or Excel 97.

<73> Section 2.4.54: Specifies Office Excel 2003, Excel 2002, Excel 2000, or Excel 97.

<74> Section 2.4.54: Specifies Office Excel 2003, Excel 2002, Excel 2000, or Excel 97.

<75> Section 2.4.74: Office Excel 2007 and Excel 2010 can sometimes save values greater than 254.

<76> Section 2.4.74: Though the maximum zero-based series number is 254, Office Excel 2007 and Excel 2010 sometimes save values greater than 254.

<77> Section 2.4.91: This structure is not loaded or saved by Office Excel 2007 and Excel 2010.

<78>
Section 2.4.97: Office Excel 2003 , Excel 2002, Excel 2000, and Excel 97
can save out 0 for this field. In these cases, if the **xfprops **field
specifies a solid fill pattern as part of the formatting properties, the
pattern's color is stored in the background color instead of the foreground
color.

<79> Section 2.4.102: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 write out this record on save.

<80> Section 2.4.102: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 do not ignore this record.

<81> Section 2.4.104: Specifies Excel 97.

<82> Section 2.4.105: Specifies Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, or Excel 2010.

<83> Section 2.4.107: Excel 97 sometimes saves out a different number of elements.

<84> Section 2.4.109: This record is always ignored in Office Excel 2007, and Excel 2010.

<85> Section 2.4.110: This record is always ignored in Office Excel 2007 and Excel 2010.

<86> Section 2.4.117: This value is always 0x0001 for files created using Office Excel 2007 and Excel 2010.

<87> Section 2.4.122: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can save out 0 for certain fonts.

<88> Section 2.4.122: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can also write out the value 0 to specify a black font, or the value 72 to specify the automatic color for a control.

<89> Section 2.4.122: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can also write out values 0 and 100 through 1000 (inclusive).

<90> Section 2.4.122: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can save values greater than 5.

<91> Section 2.4.126: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 save values of 383 to 392.

<92> Section 2.4.129: Specifies Excel 2000.

<93> Section 2.4.129: Specifies Excel 2002.

<94> Section 2.4.131: If two consecutive GelFrame records appear, the second GelFrame is a continuation of the first.

<95> Section 2.4.131: Excel 97 does not save OPT2.

<96> Section 2.4.133: Office Excel 2007 and Excel 2010 uses this GUID to determine if the VBA project needs to be recompiled on load by comparing the GUID in the file to the GUID built into the application. If the value is 0x0, the VBA project needs to be recompiled on load.

<97> Section 2.4.150: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can save any value from 0 to 0xFF.

<98> Section 2.4.154: This structure is not loaded or saved by Office Excel 2007 and Excel 2010

<99> Section 2.4.159: This structure is not loaded or saved by Office Excel 2007 and Excel 2010.

<100>
Section 2.4.191: If the value of the **wPassword** field of the Password record in the Globals Substream is not
0x0000, Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007,
and Excel 2010 encrypt the document as specified in [MS-OFFCRYPTO],
section 2.3. If an encryption password is not specified the document is
encrypted with the default password of
"\x56\x65\x6C\x76\x65\x74\x53\x77\x65\x61\x74\x73\x68\x6F\x70".

<101> Section 2.4.196: Excel 97 and Excel 2000 do not save this field as part of the record.

<102> Section 2.4.196: Excel 97 and Excel 2000 do not save this field as part of the record.

<103> Section 2.4.196: Excel 97 and Excel 2000 do not save this field as part of the record.

<104>
Section 2.4.206: If the value of the **protPwdRev** field of the Prot4RevPass record is not
0x0000, Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007,
and Excel 2010 encrypt the document as specified in [MS-OFFCRYPTO], section
2.3. If an encryption password is not specified, the document is encrypted with
the default password of "\x56\x65\x6C\x76\x65\x74\x53\x77\x65\x61\x74\x73\x68\x6F\x70".

<105>
Section 2.4.208: In the case of Excel 97 this bit specifies whether the query table adjusts column
width after refresh. If this bit is set to 1 and the **fPreserveFmt** field
in the corresponding **dwQsiFuture** field of the QsiSXTag is set to 1 then
the column width is not adjusted after refresh.

<106> Section 2.4.210: Excel 97

<107> Section 2.4.210: Excel 2000

<108> Section 2.4.210: Excel 2002

<109> Section 2.4.210: Office Excel 2003

<110> Section 2.4.210: Office Excel 2007

<111> Section 2.4.210: Excel 2010

<112> Section 2.4.210: Excel 2013

<113> Section 2.4.216: This structure is not loaded or saved by Office Excel 2007 or Excel 2010.

<114> Section 2.4.218: This record was introduced in Office Excel 2007 as a future record type. Consequently, it is preserved in BIFF8 format, but ignored by Office Excel 2003, Excel 2002, Excel 2000, and Excel 97.

<115> Section 2.4.241: If the workbook contains more than 4112 sheets, then Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can save a file in which any record that references a sheet identifier can reference the wrong sheet.

<116> Section 2.4.248: Office Excel 2007 and Excel 2010 will save at most 512 RefU in the rgref array of a Selection record. Office Excel 2003, Excel 2002, Excel 2000, and Excel 97 will save at most 1025 RefU in the rgref array of a Selection record.

<117> Section 2.4.258: This record was introduced in Office Excel 2007 as a Future Record Type. Consequently, it is preserved in BIFF8 format, but ignored by Office Excel 2003, Excel 2002, Excel 2000, and Excel 97.

<118> Section 2.4.258: This XML stream is ignored by Office Excel 2003, Excel 2002, Excel 2000, and Excel 97.

<119> Section 2.4.259: Saved only by Office Excel 2007 and Excel 2010.

<120> Section 2.4.267: Excel 97

<121> Section 2.4.267: Excel 2000

<122> Section 2.4.267: Excel 2002

<123> Section 2.4.267: Office Excel 2003

<124> Section 2.4.267: Office Excel 2007

<125> Section 2.4.267: Excel 2010

<126> Section 2.4.267: Excel 2013

<127> Section 2.4.269: Excel 2010, Office Excel 2007, Office Excel 2003, Excel 2002, Excel 2000, and Excel 97 save out an XLUnicodeString structure with 0 characters.

<128> Section 2.4.273.9: Excel 2000 has a maximum value of 8000. Excel 2002 and Office Excel 2003 have a maximum value of 32500. Values greater than these are treated as these maximums by these applications.

<129> Section 2.4.273.108: In certain circumstances Office Excel 2003, Excel 2002, and Excel 2000 can save out a higher value.

<130>
Section 2.4.281: Office Excel 2007 and Excel 2010 can save out **wbe**
with a value of 0x2B

<131> Section 2.4.310: Excel 97 does not create this field and ignores it if present.

<132> Section 2.4.324: Excel can write numbers larger than 4000 due to rounding while editing small charts.

<133> Section 2.4.324: Excel can write numbers larger than 4000 due to rounding while editing small charts.

<134> Section 2.4.324: Excel can write numbers larger than 4000 due to rounding while editing small charts.

<135> Section 2.4.324: Excel can write numbers larger than 4000 due to rounding while editing small charts.

<136> Section 2.4.325: This record was introduced in Office Excel 2007 as a Future Record Type. Consequently, it is preserved in BIFF8 format, but ignored by Office Excel 2003, Excel 2002, Excel 2000, and Excel 97.

<137> Section 2.4.326: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can sometimes save value 123820, which also indicates default theme.

<138> Section 2.4.329: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 also use the value "2" to specify justify low alignment. Justify low occurs when Arabic kashida justification is applied to the text. Justify low lengthens kashidas slightly.

<139> Section 2.4.329: Justified alignment is not supported in Office Excel 2007 and Excel 2010 and is treated as middle alignment.

<140> Section 2.4.329: Excel 97 – East Asian version, Excel 2000 – East Asian version, Excel 2002 – East Asian version, Office Excel 2003 – East Asian version, or Office Excel 2007 – East Asian version, or Excel 2010 – East Asian version.

<141> Section 2.4.335: Excel 97, Excel 2000, Excel 2002, and Office Excel 2003 do not set this bit to 1.

<142> Section 2.4.337: Excel 97, Excel 2000, Excel 2002, and Office Excel 2003 can save out a value of 0x0001, indicating that natural language formulas are enabled. This feature is deprecated in Office Excel 2007 and Excel 2010.

<143> Section 2.4.344: Stream does not exist in Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, or Excel 2010.

<144>
Section 2.4.346: Excel 97, Excel 2000, Excel 2002, Office Excel 2003,
Office Excel 2007, and Excel 2010 truncate **wScaleSLV** into a byte when
saving.

<145>
Section 2.4.346: Excel 97, Excel 2000, Excel 2002, Office Excel 2003,
Office Excel 2007, and Excel 2010 truncate **wScaleNormal** into a byte when
saving.

<146> Section 2.4.353: If the Transition Navigation Keys option is turned on, the set of prefix characters is single quote, double quote, caret, and backslash, which indicate left-alignment, right-alignment, center-alignment, and fill alignment, respectively. If the Transition Navigation Keys option is turned off, the only possible prefix character is single quote, which has no alignment significance but indicates (like all prefix characters) that the cell contents are to be treated as a string literal.

<147>
Section 2.4.353: Excel 97, Excel 2000, Excel 2002, Office Excel 2003,
Office Excel 2007, and Excel 2010 can save 0 in this field when **fStyle**
equals 1.

<148>
Section 2.5.4: Can sometimes be 0 if **year** is equal to 1900 and **month**
is equal to 1 and the calendar is Gregorian.

<149> Section 2.5.9: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can save XL8_ITBLJAPAN2, XL8_ITBLJAPAN3, XL8_ITBLJAPAN4, and XL8_ITBLNONE_JPN as 0x0000, 0x0001, 0x0002, and 0x0003. In this case, values 0x0000 through 0x0010 are saved as 0x0004 through 0x0014.

<150> Section 2.5.10: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can save bBoolErr with an error value instead of a Boolean value when fError is 0x00.

<151> Section 2.5.16: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 save out 0xFF.

<152> Section 2.5.20: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 also save out 0 to specify a black background.

<153> Section 2.5.21: The Alpha channel value in the LongRGBA structure is ignored and set to 0xFF (opaque).

<154>
Section 2.5.27: If Office Excel 2007 or Excel 2010 save different values
for **cp** in the CFEx
and CF records, then
the value in CFEx takes precedence over the value in CF.

<155>
Section 2.5.32: Office Excel 2007 and Excel 2010 will not apply any
coloring to a cell when its CFVO value falls outside of the range of the
interpolation curve and **fClamp** is not set.

<156> Section 2.5.60: Specifies Excel 97.

<157> Section 2.5.60: Specifies Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, or Excel 2010.

<158> Section 2.5.60: Specifies Excel 97.

<159> Section 2.5.60: Specifies Excel 2000.

<160> Section 2.5.63: The following table shows the maximum data functionality levels that different application versions support:

Value |
Maximum data functionality level for |
---|---|

0 |
Excel 97 and Excel 2000 |

1 |
Excel 2002 and Office Excel 2003 |

3 |
Office Excel 2007 |

4 |
Excel 2010 |

<161> Section 2.5.63: In Excel 97, Excel 2000, Excel 2002, and Office Excel 2003, the values of some data functionality level fields do not always reflect the correct data functionality level.

<162> Section 2.5.65: In the 1900 date system, Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 treat the year 1900 as though it was a leap year. That is, the value 59 corresponds to February 28, and the value 61 corresponds to March 1, allowing the (non-existent) date February 29 to have the value 60.

<163> Section 2.5.91: Office Excel 2007 and Excel 2010 sometimes saves a value greater than 15 and less than 255.

<164> Section 2.5.113: This value is only possible in the context of a Feature12 record, and cannot be written by Office Excel 2003.

<165>
Section 2.5.113: Office Excel 2003 does not save the **totalFmla**
field; **fLoadTotalFmla** is always 0.

<166> Section 2.5.118: This structure only exists in the context of a Feature12 record, and cannot be written by Office Excel 2003.

<167> Section 2.5.127: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can write out values 0x13 through 0x24.

<168> Section 2.5.129: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can sometimes save out values 511 through 1022.

<169> Section 2.5.129: These 4 default structures are saved out as identical Font structures. They are placeholders for their respective font formatting properties.

<170> Section 2.5.130: This value is ignored in Office Excel 2007 and Excel 2010.

<171>
Section 2.5.134: The Feature11
and Feature12 records set the **ref8.rwFirst**, **ref8.rwLast**, **ref8.colFirst**,
and **ref8.colLast** fields even if **fFrtRef** is 0.

<172> Section 2.5.143: Excel 97, Excel 2000, Excel 2002, and Office Excel 2003 all write out a value of 0 for this field and ignore it on load.

<173> Section 2.5.162: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 sometimes write out Icv values 0x0000 and 0x0001. Office Excel 2007 and Excel 2010 sometimes also writes out Icv values that are greater than or equal to 0x0002 and less than or equal to 0x0007.

<174> Section 2.5.164: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 sometimes writes out Icv values greater than or equal to 0x01 and less than or equal to 0x07, or the value 0x48, which specifies the system color for text in windows.

<175> Section 2.5.165: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can write values greater than or equal to 0x017F and less than or equal to 0x0188, but they will not be loaded.

<176> Section 2.5.198.18: In Office Excel 2007 and Excel 2010, natural language formulas are transformed into A1 references.

<177>
Section 2.5.198.23: Excel 97, Excel 2000, Excel 2002, Office Excel 2003,
Office Excel 2007, and Excel 2010 can sometimes write out an **rgce** which
contain PtgArray.

<178> Section 2.5.198.104: Excel 97, Excel 2000, Excel 2002 and Office Excel 2003 write out these Ptgs. Office Excel 2007 and Excel 2010 convert these Ptgs to equivalent PtgAreas or PtgAreaErrs on load and never introduces these Ptgs.

<179>
Section 2.5.203: Excel 97, Excel 2000, Excel 2002, Office Excel 2003,
Office Excel 2007, and Excel 2010 expect the **cbKey** field in the **PictFmlaKey**
structure to be an even value.

<180> Section 2.5.244: ltExternalData is only read and saved by Office Excel 2007 and Excel 2010.

<181> Section 2.5.248: Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 can save out 0 for certain fonts.

<182> Section 2.5.248: Office Excel 2003, Office Excel 2007, and Excel 2010 can also write out 0.

<183> Section 2.5.266: Office Excel 2003 has unique table identifiers per sheet rather than per workbook. On load, Office Excel 2007 and Excel 2010 reassigns new identifiers if identical ones exist within a same workbook.

<184> Section 2.5.266: Always set to 0x1 in case of Web-based data provider list data source for worksheets created using Office Excel 2003.

<185> Section 2.5.266: Office Excel 2007 and Excel 2010 will only write out the value of 1 for this field.

<186> Section 2.5.266: Office Excel 2003 saves 0xB, Office Excel 2007 saves 0xC, Excel 2010 saves 0xE.

<187> Section 2.5.266: Office Excel 2003, Office Excel 2007, and Excel 2010 do not ignore this field.

<188>
Section 2.5.272: For files last saved in East Asian versions of the
application, **lastRun** can sometimes be a Run instead of a TxoLastRun.

<189> Section 2.5.282: Specifies Office Excel 2007.

<190> Section 2.5.314: Office Excel 2007 and Excel 2010 can save values larger than 500.

<191> Section 2.5.342: Under certain circumstances, Excel 97, Excel 2000, Excel 2002, Office Excel 2003, Office Excel 2007, and Excel 2010 persist these values.

<192>
Section 2.5.344: Office Excel 2003, Office Excel 2007, and Excel 2010 can
sometimes save a value of -1 on the **itabLast** field for either a
workbook-level or a sheet-level reference to an external workbook if an Information Rights Management
(IRM) authorization failure occurred during a refresh of that workbook's
data.

<193> Section 2.6.2: Web-only view is only used by Excel 97, Excel 2000, Excel 2002, and Office Excel 2003.