The Bypass RI check box gives you the ability to turn off Referential Integrity processing for a foreign key without needing to remove the foreign key's Referential Integrity definition from the Integrity page.
When you check the "Bypass RI" check box on the Integrity page, the Referential Integrity definition on the page is bypassed when VPME enforces Referential Integrity. In other words, when a primary key in the Reference table, view or CursorAdapter is changed or deleted, the RI definition for the matching foreign key in the table, view or CursorAdapter for which you have set up a Referential Integrity definition on the Integrity page will be ignored.
Tip: When you check the Bypass RI check box, your RI definition is still used for VPM's Related Forms functionality and your Validation and Picklist Help definitions on the Integrity page still work.
Tip: You may want to use the Bypass RI feature when a foreign key is involved in multiple Referential Validation set ups. This would be the case if you have set up Referential Validation for a foreign key in a table and in views based on the table. In this case, to speed up RI processing you would want to Bypass RI for each Referential Validation setup except one.
Tip – Use View RI Definition for Performance: Previously, we suggested that you set up Referential Integrity for a view's source table, not for the view. However, Referential Integrity processing works faster for views than for tables. Therefore, when you have multiple RI definitions for a foreign key because you have set up Referential Validation for a table and views based on the table, Bypass RI for the table and all of the views except one. Use the RI definition for one of the views to update the foreign key in the table when the primary key in the Reference table, view or CursorAdapter changes or is deleted. See the next section "Referential Integrity for Views" to learn how to set up a Referential Integrity definition for a foreign key in a view.