The information in this article applies to:
SYMPTOMS
When a local view performing a Right Outer Join executes, the result set in
the view's Browse shows .NULL. in all of the left-side table's fields where
there is an unmatched row in the right-side table. If the view is defined
with an updateable left-side table when data is entered into the primary
key field of that table and the record pointer is moved, an information
message box shows the error "Update conflict" with the "OK," "Revert," and
"Help" options.
RESOLUTION
You can remove this by issuing the following command:
MORE INFORMATION
The NULL row in the view is a "virtual row" with no correspondent in the
base left-side table. If a forced update based only on the Primary Key
fails, it indicates that the base-table row is inaccessible (as is the
virtual row in the view). In this case Visual FoxPro deletes the
conflicting row from the view. Because of the soft delete mechanism in
Visual FoxPro, the user can control the visibility of deleted rows via the
command SET DELETED ON /OFF.
REFERENCESFor more information about creating Outer Joins, please see the following article in the Microsoft Knowledge Base: Q124589 How To Create a Left-right Outer Join in FoxPro for Windows Additional query words:
Keywords : kbDesigner kbVFp300 kbVFp500 kbVFp600 |
Last Reviewed: August 25, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |