>Barbara,
>Unfortunately, my co-worker has already implanted all the verification inside the DBC and to undo would be a huge mess. There is an interactive process where the user actually creates the DBC on the fly through a number of forms and the validation is then thrown into a generate DBC process. An extremely complicated process, but it meets the users needs exactly and they are extremely satisfied. The remaining issue however is this validation box (ie message box) that the dbc generates.
>
>Sandy

Sandy,

I use a 3rd party tool called xCase. It uses a template language called TCL to generate the RI rules and we have complete control over it. For example if I don't want the RI code to popup a message (because I have my own error handling for doing so), I simply need to REM (put an *) in front of that statement.

I've used field rules for over than 3 years and completely dropped them a few months ago. Consider the following case. You have a child and want to allow the user to add several fields at once before saving. We can do this by setting the buffering to 5 (optimistic table), but what happens with your field rules? They will pop at your user face everytime he moves the cursor from one record to the other...

José