Thanks for reply. I think Trigger validation is too late for the user- you want some local field validation as they navigate down form and some in final check on update (trigger ok here). You still have the problem of ugly standard message box - Do you know there any way to intercept this with error trapping ?
>>I am trying to manage field validation on a form where the underlying DBC has field rules. I find that the rule fires before the valid method and does not seem to give any opportunity to intercept the error condition. The standard message offers a Revert option but does not refresh the control so the user
>>has to re-enter the correct data.
>>Related to this issue. I have tried using a local view for the datasource and calling a fieldvalidate method which uses DBGETPROP calls to fetch the ruleExpression and RuleText for the underlying fields/record. This seems to work OK but I am still trying to determine what type of datasource I have -
>>Table, Localview or Remoteview. Is there a function call which returns this information for a given alias()?
>
>Personally, I recommend to do validation through triggers. These fire only when you do TableUpdate().
>
>Hilmar.