Hi David,

One of us is not understanding the other. I hope it's me that doesn't understand you. I can't see how the RI has anything to do with what I'm looking for. Though it's very possible that I don't understand the RI completely.

I'm trying to create a generic Field Validation Rule that can determine if the event that triggered the Validation Rule was just normal data entry in the field or a TABLEUPDATE() from a VIEW that has already done the Validation on this field.

I looked at the array and can see that a TABLEUPDATE() was issued and what prg/method issued it, but it doesn't seem to help. I can already determine that the Validation Rule was run from a view and even what view ran it. But I can't determine if the TABLEUPDATE() being executed is from a view that has already run the Validation Rule.

In theory I could have 2 views open at the same time. One of them has a field Validation Rule (same Rule as the underlying table), but the other doesn't. I'm trying to prevent the Validation Rule from executing when the 1stt view TABLEUPDATEs(), but it still needs to execute when the 2nd view TABLEUPDATEs().

It just now occured to me, that I could test the DataSession. I can't think of any time that I would have 2 views open in the same DataSession that update the same table. If the Validation Rule has been run from a view in the current DataSession then don't run it again during a TABLEUPDATE().

Thanks for the reference to ASTACKINFO(). It does allow me see that TABLEUPDATE() was issued. I've only been working in 7.0 for a few weeks and haven't discovered all the new stuff.


>Bill,
>
>Did you look at the array to tell if there is already something in the callstack that will tell you what you are looking for? I would think that the functions/methods of the RI are there in the stack.
>
>>Did you have an idea on how I could use this? The only thing I can think of is to wrap the TABLEUPDATE() in a PRG and test for the PRG in ASTACKINFO().