C
Constantin
For work, I depend on creating excel files with hundreds of cell name references. These references allow me to use plain english names for variables rather than hardcoded cell references (i.e. "Labor_Rate" vs. "Worksheet1!A:2").
When I open a Excel '97 file from my work computer in Mac Office 2008, the file is fine initially - all calculations work, all references are OK. However, if I duplicate a worksheet within the workbook that refers to these fields, then all references on some (but not all) sheets get wiped out. From what I can tell, the cell references in the leftmost worksheet remain valid, the references to cells in the remaining worksheets get broken.
Note, I am not copying a worksheet that contains these references. I am simply copying a worksheet that depends on them. As a result of this error, my entire workbook goes from executing fine to being filled with REF! errors. This was not a problem under Office 2004 for the Mac. There is no VB involved either...
Any suggestions what might be causing this and how to work around it (other than reverting to Office 2004)? Alternatively, if someone could point me in the right direction re: reporting bugs to the Mac BU, that would be great also. Oh, and if it's any help, I'm running 10.5.1 with all the patches on an Intel-based MacBookPro.
When I open a Excel '97 file from my work computer in Mac Office 2008, the file is fine initially - all calculations work, all references are OK. However, if I duplicate a worksheet within the workbook that refers to these fields, then all references on some (but not all) sheets get wiped out. From what I can tell, the cell references in the leftmost worksheet remain valid, the references to cells in the remaining worksheets get broken.
Note, I am not copying a worksheet that contains these references. I am simply copying a worksheet that depends on them. As a result of this error, my entire workbook goes from executing fine to being filled with REF! errors. This was not a problem under Office 2004 for the Mac. There is no VB involved either...
Any suggestions what might be causing this and how to work around it (other than reverting to Office 2004)? Alternatively, if someone could point me in the right direction re: reporting bugs to the Mac BU, that would be great also. Oh, and if it's any help, I'm running 10.5.1 with all the patches on an Intel-based MacBookPro.