BUG: Sequential File I/O Does Not Handle Embedded Nulls (142246)
The information in this article applies to:
- Microsoft Visual Basic Learning Edition for Windows 5.0
- Microsoft Visual Basic Learning Edition for Windows 6.0
- Microsoft Visual Basic Professional Edition for Windows 5.0
- Microsoft Visual Basic Professional Edition for Windows 6.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
- Microsoft Visual Basic Standard Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic for Applications 5.0
This article was previously published under Q142246 SYMPTOMS
Using sequential file I/O to read in file that contains embedded null
characters (characters with an ANSI value of 0) can cause the following
error message:
"Run-time error '62':
Input past end of file".
STATUS
Microsoft has confirmed this to be an issue in the Microsoft products
listed at the beginning of this article. Microsoft is researching this
issue and will post new information here in the Microsoft Knowledge Base as
it becomes available.
RESOLUTION
You can work around this behavior by opening the sequential file as a
binary file and manipulating the sequential file as a binary file using the
Get and Put statements to set and retrieve file data.
REFERENCES
For additional information, please see the following article(s) in the
Microsoft Knowledge Base:
140354 BUG: Input Function Doesn't Ignore EOF
Modification Type: | Major | Last Reviewed: | 5/7/2003 |
---|
Keywords: | kbbug KB142246 |
---|
|