Correction:

The issue shows itself within Excel 2003 currently. It may happen in
some instances of Excel 2010 but this is yet to be rolled out for our
customers and thus, we are unsure. Any solution must be compatible for
both