>>I don't think there is. And I think what you really need in this case is to evaluate whether the rule is to evaluate all the rules, and then decide for yourself what to do about this. I mean, this gives you more power. For instance, you can evaluate all the rules, and then show a user a dialog with all the violations, for instance:
>>
>>Can't save the record, for the following reasons:
>>
>>Field1 must have a value.
>>Field2 must have a value.
>>Field3 is duplicate.
>>
>
>What if the fields are wide and varid placed on the form. He might end up click at diff. places to get the results back to normal. I do it in the txt.valid() using dbgetprop() right now and also change its color to red.

Well, there are different ways to do this validation. My personal preference is to do all the validation only when the user tries to save - but I was forgetting, in my previous suggestion, that field-level rules can interfere in this case.