PRB: Distribution Kit on LAN Leaves Temporary Files Behind

Last reviewed: April 17, 1995
Article ID: Q87664
The information in this article applies to:
  • Microsoft FoxPro for MS-DOS, version 2.0

SYMPTOMS

While compiling an .EXE file, the process stops with a "Cannot open file" or a "Error 3008:Cannot open file ..." error message that refers to a distribution kit program file. If the user is given all access rights (except for delete) to the program directory, the program compiles correctly. However, the compilation process leaves several files in the program directory with names like WLK02112.--a, WLK02112.--b, WLK02112.--c, and so on.

CAUSE

Compiling program files in the FoxPro Distribution Kit places the temporary files in the directory from which the user starts FoxPro. Or, if the "SET TEMP=<path name>" command is used in the AUTOEXEC.BAT file, the temporary files are placed in the path specified in this command. The TMPFILES statement in the CONFIG.FP file does not affect file placement.

RESOLUTION

Include the fully qualified path to the network drive and directory where the FoxPro Development and Distribution programs are installed. Start FoxPro from a user directory that has all rights, including erase or delete rights, assigned to it. The process of compiling using the Distribution Kit creates files in and deletes files from the user directory. The system administrator can designate the program directory read only.


Additional reference words: FoxDos 2.00 build executable stand-alone
application
KBCategory: kbtool kbnetwork kberrmsg kbprg kbprb
KBSubcategory:


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: April 17, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.