How to Eliminate RI Rule Code from a .DBC File

Last reviewed: February 8, 1996
Article ID: Q145752
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, versions 3.0 and 3.0b

SUMMARY

This article explains how to remove the Referential Integrity rules from a database container (.dbc file) object.

MORE INFORMATION

There may be circumstances where you have added Referential Integrity (RI) to a database but then later decide you no longer want the RI code in the database. You can start over after deleting all the old RI rules.

the safest (and preferred) way to do this is to go into the Referential Integrity builder and set all options (Update, Delete, and Insert) on the tables to Ignore. Then generate the RI code again. This method will eliminate the stored procedures in the database. This process is tedious, however, and if the .dbc file contains many tables, it may take a long time. Also, the RI Builder puts some default code into the stored procedures even when Ignore is chosen, but the code isn't used unless RI code (Cascade or Ignore) is generated.

CAUTION: The following method will remove any and all stored procedures from your database container. This means that if you have any custom code in SPs, the code will be deleted. Therefore, you should use the following method only in cases where you only want to strip out RI code.

Alternatively, you can open the .dbc as a table and manipulate the code manually. The following commands create the same end result as the first method:

   REPLACE ALL Riinfo with ''
   REPLACE CODE WITH "" FOR Objectname='StoredProceduresSource' or ;
      Objectname='StoredProceduresObject'


Additional reference words: VFoxWin 3.00 3.00b delete
KBCategory: kbtool kbhowto
KBSubcategory: FxtoolDbtabledes


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: February 8, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.