Microsoft KB Archive/89181

= How to use a program to perform an outer join that preserves all records in the parent table and processes the nested SELECT-SQL statements in FoxPro =

Article ID: 89181

Article Last Modified on 3/17/2005

-

APPLIES TO


 * Microsoft Visual FoxPro 3.0 Standard Edition
 * Microsoft Visual FoxPro 5.0 Standard Edition
 * Microsoft Visual FoxPro 6.0 Professional Edition
 * Microsoft FoxPro 2.0
 * Microsoft Visual FoxPro 3.0b for Macintosh

-



This article was previously published under Q89181





SUMMARY
When FoxPro Relational Query By Example (RQBE) is used to join two tables, a record in the parent database that does not have any corresponding record in the child table is omitted from the joined database. However, under some circumstances, this is not the desired behavior. The text below details how to perform an &quot;outer join&quot; that preserves all records in the parent table.

NOTE: The RQBE interface cannot perform an outer join; a program must perform the join because the RQBE interface cannot process the necessary nested SELECT-SQL statements.



MORE INFORMATION
The code below demonstrates an outer join of the CUSTOMER.DBF and INVOICES.DBF tables in the FOXPRO2\TUTORIAL directory.

NOTE: In Visual FoxPro for Windows, open the CUSTOMER.DBF and ORDERS.DBF files in the VFP\SAMPLES\MAINSAMP\DATA subdirectory. Then, substitute CUSTOMER.CUST_ID for CUSTOMER.CNO, and ORDERS.ORDER_ID for INVOICES.INO in the code below.

(Note that the space before each semicolon [;] character is required. Omitting the space from the query causes an error.) SELECT customer.company, customer.cno, invoices.ino ; FROM customer, invoices ; WHERE customer.cno = invoices.cno ; UNION ; SELECT customer.company, customer.cno, 0 ; FROM customer ; WHERE customer.cno NOT IN ; (SELECT invoices.cno FROM invoices ;           WHERE customer.cno = invoices.cno) ; INTO CURSOR QUERY The lines from the first SELECT statement to just before the UNION statement SELECT customer.company, customer.cno, invoices.ino ; FROM customer, invoices ; WHERE customer.cno = invoices.cno ; select all the records in the parent table that have a corresponding record in the child table. This is what you normally get when you do a join. The UNION statement tells FoxPro to include the output of the first half of this SELECT-SQL statement with the second half in the final results. It is important that the data in the second half of the query have the same structure as the data in the first half of the query, otherwise errors are generated.

The lines after the UNION statement SELECT customer.company, customer.cno, 0 ; FROM customer ; WHERE customer.cno NOT IN ; (SELECT invoices.cno FROM invoices ;           WHERE customer.cno = invoices.cno) ; retrieve all of the records in the parent tables that have no corresponding child record. This is done as follows:

  The SELECT-SQL statement in the parentheses creates a list of all the records that have corresponding child records. (SELECT invoices.cno FROM invoices ;        WHERE customer.cno = invoices.cno) ;   The SELECT-SQL statement directly above that then selects all the records that are not in the list created by step 1. SELECT customer.company, customer.cno, 0 ; FROM customer ; WHERE customer.cno NOT IN ;  The 0 in the line for the second SELECT-SQL statement is used as a placeholder. If INVOICES.INO is a date field, use { / / } instead of the 0. Similarly, if INVOICES.INO is a character field, use &quot; &quot;. The idea is for the placeholder to be the same type as the field that it replaces.

Please note that at this time, there are no plans to implement the functionality for a memo field placeholder. However, a workaround for this situation is documented in the following article in the Microsoft Knowledge Base:

119901 How to Use the UNION Clause in a FoxPro SELECT Statement



If the ORDER BY clause is entered at the end of the SELECT statement, and the CNO field is used, an error message occurs. For example, the following clause ORDER BY cno results in an &quot;Fieldname is not unique and must be qualified&quot; error message. Similarly, the following clause ORDER BY customer.cno results in an &quot;SQL Invalid Order by&quot; error message.

To eliminate these errors, use the ORDER BY clause with a column number. For example, the following clause ORDER BY 1 results in a query ordered by CNO since CNO is in column 1 of the output table.

Additional query words: VFoxMac FoxDos VFoxWin FoxWin 2.50 2.50a 2.50b kbvfp300 kbvfp500 kbvfp600 kbdatabase 2.60 2.60a

Keywords: kbcode KB89181

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.