Actually, I'm looking for a way for the validation rules to AUTOMATICALLY recognize that the field has already been validated (in the view) and not execute again.

I'm hoping that there is some way for the rule to recognize that TABLEUPDATE() is executing and just return .t.

Or in the alternative, somehow have the rule set a flag when the view is being edited, so that when TABLEUPDATE() is issued 1) the rule won't execute and 2) clear the flag. But the flag would also have to be cleared if TABLEUPDATE() is not issued.


>Either don't copy validations into view or have some flag, which can trigger validations if needed. Your validation rule would be:
>(vartype(myFlag)='L' and not myFlag) or myRule()
>
>So, if you set myFlag to .f. your validations would return .t. without firing the rule.
>
>>I'm using VFP 5.0a
>>
>>All my views have the field validation rules copied from the underlying tables.
>>
>>I'm looking for a way to keep the field validation rules from executing twice, 1st when the view is edited and 2nd when TABLEUPDATE() is issued.
>>
>>Any ideas?
>>
>>TIA