RQBE Creates UNTITLED.QPR File in Current Directory

Last reviewed: April 29, 1996
Article ID: Q93327
The information in this article applies to:
  • Microsoft FoxPro for MS-DOS, versions 2.0, 2.5x, 2.6x
  • Microsoft FoxPro for Windows, versions 2.5x, 2.6x

When a Relational Query By Example (RQBE) session begins, Microsoft FoxPro creates a temporary file named UNTITLED.QPR in the current (default) directory.

FoxPro uses the UNTITLED.QPR file as a temporary storage area for the SQL SELECT statement. When the user chooses See SQL in the RQBE window, FoxPro displays the contents of the file. FoxPro creates the UNTITLED.QPR file regardless of the EDITWORK, SORTWORK, PROGWORK, and TMPFILES settings in the CONFIG.FP file.

If the user begins an RQBE session on a network drive on which the user does not have both create and delete rights, either of two error messages appear: "File access denied" or "Cannot create file." To address this situation, use the SET DEFAULT TO statement to specify a default directory on which the user has create and delete rights.

The "File access denied" error also occurs when two users have their default directory pointing to the same network directory and the second user attempts to open a new query. The UNTITLED.QPR file cannot be modified by two users at the same time (which is true for any program file).

NOTE: In Visual FoxPro for Windows, RQBE has been replaced by the Query Builder, which does not have this problem.


Additional reference words: FoxDos FoxWin 2.00 2.50 2.50a 2.60 2.60a tshoot
errmsg err msg
KBCategory: kbprg kberrmsg
KBSubcategory: FxtoolRqbe


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 29, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.