The information in this article applies to:
SYMPTOMSYou compile a Visual FoxPro program file, form, class library, or report that contains at least one compile error. SET LOGERRORS is ON, which is the default, and this forces Visual FoxPro to write any compile errors to a .ERR file. When the .ERR file is opened within the Visual FoxPro editor, it will appear as expected with line feeds between each line, but if the file is opened with another editor, such as Notepad, no line feeds appear, and the text will all appear on a single line. CAUSEThe .ERR file is written with a carriage return character (ASCII value 13) at the end of each line, but no line feed character (ASCII 10). The Visual FoxPro editor moves to a new line with each ASCII 13 character, but other editors such as Notepad may not. STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why MORE INFORMATIONSteps to Reproduce Behavior
MOTE: If you are running Visual FoxPro 3.0 or 5.0, then you must create the program file manually. The STRTOFILE function is not available in earlier versions of Visual FoxPro.
REFERENCES© Microsoft Corporation 1999, All Rights Reserved. Additional query words:
Keywords : kbVFp300bbug kbVFp500abug kbVFp600 kbVFp600bug kbXBase kbVS600sp3fix kbGrpFox |
Last Reviewed: June 7, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |