PRB: Using RQBE, the See SQL Information Is Not Updated

Last reviewed: April 29, 1996
Article ID: Q100557
The information in this article applies to:
  • Microsoft FoxPro for Windows, versions 2.5 and 2.5a

SYMPTOMS

When you are creating a query using the Relational Query By Example (RQBE) tool and sending the output to a table/.DBF, the name of the table in the SQL statement is not properly updated if you change the text in the Name box.

RESOLUTION

To work around this problem, use the mouse or the TAB key to place the insertion point (cursor) in the Name box, and then choose the See SQL button.

NOTE: Visual FoxPro for Windows uses its Query Designer instead of RQBE.

MORE INFORMATION

Steps to Reproduce Problem

  1. Issue the following commands:

          USE tutorial\customer.dbf
          MODIFY QUERY test
    

  2. In the Output box, select Table/DBF.

  3. In the Save As dialog box, name the output table JUNK.DBF.

  4. In the selection criteria, select CNO for Field Name, select Like, and type "a" (without the quotation marks) in the Example box.

  5. Choose the See SQL button. Note that the information is correct. Close the TEST.QPR window.

  6. In the Name box, change the name to JUNK1.DBF.

  7. With the mouse, change the Example box of the selection criteria to read "ab" (without the quotation marks).

  8. Choose the See SQL button. Note that the table name is not updated to JUNK1.DBF.


Additional reference words: FoxWin 2.50 2.50a
KBCategory: kbprg kbprb
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.