>Thank Hilmar
>
>>dbgetprop("Field") and dbgetprop("Table") seem to be appropriate for this purpose.
>I already am using dbgetprop() from the textboxes based on the control source. I thought that there might be a way to fire manually like
>
>DBCName.FireFieldValidation(this.controlsource)
>
>just to give the idea <g>.
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.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
