Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a workbook that we have been using daily for many years in Excel 2003.

We are now migrating to Excel 2010, and have encountered the following problem.

When the workbook is opened in 2010 (32-bit version on 64-bit Windows 7) (clean open, no other workbooks present) and we try calculating any of the worksheets (even the simplest one), we get the following error:

"Microsoft Excel cannot calculate a formula. There is a circular reference in an open workbook, but the references that cause it cannot be listed for you. Try editing the last formula you entered or removing it with the Undo command."

This does not seem to happen in the 64-bit version of 2010.

If we open the workbook in Excel 2003, there are no calculation issues. If we open the workbook in 2003 and calculate one sheet (shift-F9), or even calculate one cell that is a trivial reference to another cell (=E4), and then save the workbook, we do not get quite the same behaviour: when opened in 2010, we can calculate various sheets (shift-F9 or worksheet.calculate), but when running a macro to calculate all sheets in the workbook, it crashes at some point on one of the sheets. Again, this does not happen in the 64-bit version of 2010.

Has anyone else encountered this problem with Excel 2003-workbooks in Excel 2010, 32-bit version? I cannot find any references to a problem of this description anywhere. Thanks.

share|improve this question
Did you convert the file before calculating? – CharlieRB Jul 30 '13 at 19:00
I think I'm thinking the same as @CharlieRB. Have you tried saving the file as xlsm / xlsx? There might be some info from the 2003 version that isn't being understood correctly for Excel 2010. Saving it as the new file type might correct that. – joseph4tw Jul 31 '13 at 2:55
Well, my concern isn't really with "correcting" the spreadsheet. The spreadhseet gets produced by a fairly complex automated process and needs to be operable for a number of fairly complex processes that follow. I can perhaps "correct" it in one instance for 2010-32bit, but that gives me no guarantees that it will be corrected in future instances unless I know and understand the problem exactly. In other words, I am looking to understand what the problem is, not just figure out a hack to get around it. (Indeed, if you re-read my post, I indicate one way to "correct" it already.) – David I. McIntosh Aug 1 '13 at 3:41

You must log in to answer this question.

Browse other questions tagged .