XL98: Error Message Cut Off Running Code in Immediate Window (176158)
The information in this article applies to:
- Microsoft Excel 98 Macintosh Edition
This article was previously published under Q176158 SYMPTOMS
When you execute a line of Microsoft Visual Basic for Applications code, if
the line of code cannot be executed, you may receive a truncated error
message.
For example, if you execute a statement that involves a file called
"SomeFileWithALongFileName" that does not really exist on your computer,
you may receive the following error message:
Run-time error '1004':
'SomeFileWithALongFileName' could not be found. Check the spelling of
the file name, and verify that the file location is correct.
If you are trying to open the file from your list of most recently
used files on the File menu, make
The correct error message that you expect to receive is:
Run-time error '1004':
'SomeFileWithALongFileName' could not be found. Check the spelling of
the file name, and verify that the file location is correct.
If you are trying to open the file from your list of most recently
used files on the File menu, make sure that the file has not been
renamed, moved, or deleted.
Note the additional text after the word "make" in the preceding paragraph.
CAUSE
This problem occurs when the following conditions are true:
- You execute the code from the Immediate window. (In the Visual Basic
Editor, click Immediate Window on the View menu, or press COMMAND+G.)
-and-
- The length of the error message exceeds 255 characters.
NOTE: This problem does not occur in Microsoft Excel for Windows.
WORKAROUNDMicrosoft 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 see the entire error message, run the code as part of a Visual Basic
Sub procedure (or macro) in a module. For example, instead of running the
following line of code in the Immediate window:
Workbooks.Open "Macintosh HD:SomeFileWithALongFileName"
type the following macro into a module and run it:
Sub Test()
Workbooks.Open "Macintosh HD:SomeFileWithALongFileName"
End Sub
When you run the macro from a module, the entire error message is
displayed.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article. We are researching this problem
and will post new information here in the Microsoft Knowledge Base as it
becomes available.
MORE INFORMATION
The length of the first error message listed in the "Symptoms" section of
this article (the error message that ends with the word "make"), is exactly
255 characters, including carriage returns. Because the correct, complete
error message is longer than 255 characters, the error message is cut off
when you run the code in the Immediate window.
REFERENCES
For additional information about getting help with Visual Basic for
Applications, please see the following article in the Microsoft Knowledge
Base:
163435
VBA: Programming Resources for Visual Basic for
Applications
| Modification Type: | Minor | Last Reviewed: | 9/12/2006 |
|---|
| Keywords: | kbbug kbdtacode kberrmsg KB176158 |
|---|
|