Article ID: 236299 - View products that this article applies to.
This article was previously published under Q236299
In Microsoft Excel 2000, when you try to open a file that was saved in Excel 97, you receive an error message similar to the following:
If you click Yes you receive the following error message
An error occurred while loading 'Sheet111111111111111111111111111'. Do you want to continue loading the project?
with details similar to the following:
This program has performed an illegal operation and will be shut down.
If you click No you receive the error message
EXCEL caused an invalid page fault in module VBE6.DLL at 0167:650f6290.
and Excel does not open the file.
File not found.
These problems occur when the following conditions are true:
To work around this problem, use either of the following methods.
Copy to a New WorkbookOpen the problem file in Excel 97, and copy all but the sheet with the longest (Name) property to a new workbook. You can now open this workbook in Excel 2000.
Use the Microsoft Excel 97 File Recovery Macro
Macro to Prevent This Problem in the FutureMicrosoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
To prevent this problem in the future, you can use macro code similar to the following in your Visual Basic for Applications macros. The following procedure uses the Sheets.Add method instead of the built-in ActiveSheet.Copy macro command. The procedure then copies the information from the original sheet to the newly created sheet. Because this method uses a different naming convention, it avoids the problem.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Microsoft has changed the way Excel names a copy of a worksheet in Visual Basic for Applications. In Excel 97, when you copy a worksheet, Visual Basic for Applications gives the new worksheet a (Name) property by adding a 1 to the end of the (Name) property of the original sheet. If the (Name) property of the original sheet is "Sheet1", the (Name) property of the copied sheet becomes "Sheet11". This fails after a number of iterations, when the sheet (Name) property becomes longer than 32 characters. At this point, Excel 97 stops responding (crashes).
In Excel 2000, Visual Basic for Applications numerically increments the (Name) property, rather than adding a 1 on the end. Therefore, this problem is not likely to occur when you make multiple worksheet copies in Excel 2000.
To view the (Name) property, follow these steps:
This same error message occurs if you delete the last worksheet copied and save the file.
Excel has caused an invalid page fault in module Ole32.dll at 015f:7ff3da31
For more information about how to move or copy sheets , click Microsoft Excel Help on the Help menu, type Move sheets in the Office Assistant or the Answer Wizard, and then click Search to view the topic.