I'm trying to bullet proof a generic PRG that prevents field validation rules from running during a TABLEUPDATE() from a View when the View has already run the rule.

Is there any way that a generic field validation rule can determine :
1. the field being validated ?
2. whether TABLEUPDATE() is being used to trigger the rule ?
3. the View that is being TABLEUPDATEd() ?

If these things are not determinable from within the PRG, then I will probably end up wrapping the TABLEUPDATE() in a PRG, which probably isn't a bad idea anyway.


TIA