As Posted here and verified by me.
I don't have what I'd call a "satisfactory" resolution, but I do have a workaround (kindof!)
Round trip the file using Excel 2003 to remove corruption if the work book will not repair in 2010:
- Open the file in Excel 2003
- Go to File: Save
- Change the Save As type to Web Page (.html), save and close the file
- Open the .html file in Excel
- Save the file as a .xls (with a new name so the original isn't lost)
I do not know where the actual "corruption" comes from.
Evidently Office 2010 is much more "picky" about checking files for issues than office 2003.
According to Microsoft:
“Please keep in mind that it's often quite difficult, if not impossible, to determine where corruption comes from. Corruption can exist in the "shell" of the workbook, or in certain areas, such as a PivotTable, styles, defined names, objects, or the calculation chain/formulas. Corruption can be caused by many different scenarios, for example, a network glitch while saving, a power surge, copying and pasting in corruption from another file, the list goes on. You can compare file corruption to getting a nail in your tire. The nail may be stuck in your tire for a long time without you even noticing, and then all of a sudden your tire goes flat, or the file becomes unreadable or displays strange symptoms.”
I think it's a poor analogy, but I hope this helps.
Before you import the file from other system, change the name of the worksheet of the workbook. Longer names cause problems in conversion