FIX: RI Code Not Selecting Right Work Area After Cascaded Delete (221648)
The information in this article applies to:
- Microsoft Visual FoxPro for Windows 5.0
- Microsoft Visual FoxPro for Windows 5.0a
- Microsoft Visual FoxPro for Windows 6.0
This article was previously published under Q221648 SYMPTOMS
You have a database container (DBC) that contains several tables. The DBC contains referential integrity code generated by the Referential Integrity (RI) Builder. The RI is configured to cascade deletes from a parent to a child table, and from the child table to another child table. When a record is deleted from the parent table, the stored procedure that performs the cascaded delete does not immediately reselect the correct work area after the delete occurs.
CAUSE
In the code created by the Referential Integrity Builder, the local variable lcStartArea is declared in both the insert and update code, but not in the delete code.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in Visual Studio 6.0 Service Pack 3.
For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base: 194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed
Modification Type: | Major | Last Reviewed: | 10/15/2002 |
---|
Keywords: | kbBug kbCodeSnippet kbDatabase kbDSupport kbVS600sp3fix KB221648 |
---|
|