Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 211
  • Last Modified:

Error in Excel 2003 but not 2010

I created a workbook that has a ton of formulas and a few macros in Excel 2003 and tested the workbook with the end user community.  After we released the workbook for production processing people in the field started getting the following error after saving and trying to reopen:

Excel found unredable content in 'filename.xls' Do you want to recover the content of this workbook?

This is happening intermittently and the file open no problem in Excel 2010 without any error's reported.  I have to figure out why this is happening as there are about 100 instances of this workbook in the field right now and this is happening to about 15 of the workbooks.  I did find circular references in one case but not all when I opened in 2010 and eliminating all circular references fized the problem and I was able to open in 2003 again without losing anything.  This was only true in one case though and I can not find circular references in any of the others that had errors.  Has anyone ever seen this happen before and is there a logical solution?
0
R_M_Ron
Asked:
R_M_Ron
1 Solution
 
jppintoCommented:
Please check this:

http://support.microsoft.com/kb/929766

jppinto
0
 
FernandoFernandesCommented:
check the names collection through VBA,
Alt F11
Ctrl+G
Type: ?activeworkbook.Names.count
then enter.
if the number is higher than 65472, then u need to clear names until the number is below that. You can only do it with Excel 2007 or 2010, since 2003 will always think the file is unreadable.
More:
excessive number of formats/validations/conditional formatting, also can break the file, but not make it unreadable. The best suggestion is if you could, upload the file, then I can make thorough investigation with it.

if u cant, u could do it yourself starting with check compatibility under File/Info (Office 2010)...

and you should have all your field usin the same version of Excel, it's safer! And the file itself should be the new xml formats instead of the old format as the new format does not have the limitations mentioned in this post.

hope it helped somehow!
0
 
clarkscottCommented:
I suggest you do all the editing using Excel 2003.  2010 will 'convert' everything upon opening, but 2003 won't convert 2010 stuff (even if the code is the same).   This also pertains to REFERENCE Files.  If you do all your work in 2003, 2010 will (hopefully) automatically assign the 'next version' of the ref. file.  This process does NOT work backwards.  If you write in 2010 (even if in 'converted mode'), the reference files 2010 uses will crash in 2003.

I don't know if this is your solution... but it's good to remember.

Scott C
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
R_M_RonAuthor Commented:
Thank you everyone for the leads here.  I am getting back to this tonight and will try all of these solutions (I got bogged down with server admin tasks today so looks like I will be working this late again tonight)
0
 
R_M_RonAuthor Commented:
This ended up being related to Defined Names that were causing problems with data validation ranges.  The defined names were in an older version (that I did not create) and I never removed the references to the names.  Not sure why they were corrupting the file but when I deleted the invalid named ranges in 2010 and saved, I was able to open in 2003 again and could not cause the same problem.  You saved me a TON of headache. THANKS!!!!!
0
 
FernandoFernandesCommented:
:)
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now