Pitchblend
New Member
- Joined
- Feb 16, 2012
- Messages
- 44
It is possible that at least 1 person is aware that I have been struggling with data integrity issues when translating files from Excel 2003 to Excel 2007 for the last several weeks.
One issue that we have identified today is that if the 2003 Workbook contains named ranges, each range name must be checked to make sure they the name does not confict with reserved range names in Excel 2007+.
Range names that are causing problems
DAT1, DAT2, DAT3 .....
Jul04, May10 ....
You get the idea. Sometimes you will get a notice of minor loss of fidelity when saving 2003 to 2007 - but don't count on it!
Perhaps one of our highly valuable but under-appreciated MVP's or MODERATORS can expand on this issue?
Currently, we are thinking that all named ranges in all Excel 2003 workbooks will need to be reviewed. Perhaps someone out there can suggest a better fix - maybe an audit tool?
One issue that we have identified today is that if the 2003 Workbook contains named ranges, each range name must be checked to make sure they the name does not confict with reserved range names in Excel 2007+.
Range names that are causing problems
DAT1, DAT2, DAT3 .....
Jul04, May10 ....
You get the idea. Sometimes you will get a notice of minor loss of fidelity when saving 2003 to 2007 - but don't count on it!
Perhaps one of our highly valuable but under-appreciated MVP's or MODERATORS can expand on this issue?
Currently, we are thinking that all named ranges in all Excel 2003 workbooks will need to be reviewed. Perhaps someone out there can suggest a better fix - maybe an audit tool?