PRB: Copy To ... Type SDF Causes Error Message in Visual FoxPro

Last reviewed: September 11, 1997
Article ID: Q172923
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, versions 5.0, 5.0a

SYMPTOMS

Issuing two consecutive COPY TO <filename> TYPE SDF commands causes Visual FoxPro 5.0x to return the following error message on the second command:

   File <filename>.txt already exist as part of a database.

This error does not occur in Visual FoxPro 3.0b.

RESOLUTION

Check for the existence of the first SDF file and if it exists delete it. In the code example in the MORE INFORMATION section below, the following code accomplishes this task. Place the code between the two COPY TO commands:

   IF FILE("test1.txt")=.t.
      DELETE FILE test1.txt
   ENDIF

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The error message occurs only when zero (0) is the first character in the SDF file. However, if the resulting SDF file is smaller than 8000 bytes, the error does not occur even if the zero character is in the SDF file. Finally, choosing any other file format or placing any other character in the SDF file prevents the error.

Steps to Reproduce Behavior

Create a program that contains the following code and execute it:

   CLEAR
   CREATE TABLE test1.dbf FREE (f C(100))
   FOR i = 1 TO 80
      INSERT INTO test1 VALUES ("0")
   NEXT
   COPY TO test1.txt TYPE SDF
   COPY TO test1.txt TYPE SDF

The error appears on the second COPY TO command.


Additional query words: sdf
Keywords : FxprgGeneral vfoxwin
Version : WINDOWS:5.0,5.0a
Platform : WINDOWS
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.