While being bound to Excel 11 (aka 2003) 10 (aka 2002)^*) and above might be bearable — depending on your environment and what you need it for —, the more severe problem I found with this approach is the internal optimization Excel performs with empty cells.

Excel will drop <Cell> tags if no "significant" data or format information has to be saved there. Instead the next cell in the output will get an attribute to indicate its column position in the worksheet instead.

Suppose you have a row which looks similar to

data

more data

…

Then your XMLSS output might look somewhat like:

<Row>
  <Cell>
    <Data ss:Type="String">data</Data>
  </Cell>
  <Cell ss:Index="3">
    <Data ss:Type="String">more data</Data>
  </Cell>
  ...
[download]

which makes it harder than necessary for my taste to navigate to the cells in search for.

Update: ^*) I now think XML-Spreadsheet (XMLSS) export was introduced with Excel 10 ->MSDN

---

In reply to Re^2: Read Excel cell comments? by pKai
in thread Read Excel cell comments? by AlwaysLearning

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.