PRB: Referential Intregrity Builder Leaves Code BehindID: Q131460 3.00 3.00b WINDOWS kbprg kbprb The information in this article applies to:
SYMPTOMSThe Referential Integrity (RI) Builder leaves code in the Stored Procedures even when all the Trigger options are set to IGNORE.
WORKAROUNDThe RI Builder copies the existing contents of the Stored Procedures to a file called RISP.OLD before it makes any changes, so you can recover modified procedures and paste them into the current Stored Procedures.
STATUSMicrosoft is researching this behavior and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
Steps to Reproduce Behavior1. Type the following commands in the Command window:
2. Double-click the Persistent Relation line that connects the two tables.
3. Click the Referential Integrity button to invoke the RI Builder.
4. In the RI Builder, change any of the Triggers from "Ignore" to something 5. In the Edit Relationship dialog box, click OK.
6. Enter the Stored Procedures, note the code the RI Builder produced. 7. Return to the top of the Stored Procedure file.
8. Add a comment to the "RIDELETE" procedure. 9. Close the Stored Procedure Window. 10. Repeat Steps 2 and 3 above. 11. Set all the Triggers back to "Ignore." 12. Repeat Steps 5 and 6. 13. Note the generic procedures that the RI Builder created are still in 14. Type the following command in the Command window:
15. Note the comment made in Step 8 exists here. You could cut and paste
Additional reference words: 3.00 3.00b VFoxWin
KBCategory: kbprg kbprb
KBSubcategory: FxprgTable
|
Last Reviewed: May 1, 1996 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |