Nadya --

I guess I can live with that kind of annoyance. In fact, I'd say that there are always minor things like that that I can't get to work exactly as I'd like. Over time, as I've learned more, the frequency has been diminishing, but I can't invest the time to perfect every screen I work on.

Cheers,

Jim

>>Nadya --
>>
>>Two different issues. I'm just interesting in doing some checking to determine whether it is permissible to leave the current page. Knowing that I can use NODEFAULT is sufficient.
>>
>>Your problem, as I recall, was something different, something about wanting to only do something the first time Deactivate is called for a page, but not thereafter. I don't recall either why you were trying to do so or why you were unable to do so. I had suggested keep track of the number of the most recently deactivated page, but apparently that suggestion didn't help (or was irrelevant, I guess).
>>
>>Cheers,
>
>James,
>
>I have the exact same requirements as you do. If there are penging changes, I want to ask a question and depending on the answer, take the appropriate action. NODEFAULT in Deactivate works nicely. There is only one problem (if we're not going to mention -> and <- behavior): the deactivate fires even if you click on the same tab. So, you're not leaving a page, but you're asked anyway. That's a little bit on annoyance...
>
>
>In other words, the problem is very simple: from the Page Deactivate there is NO WAY to determine, what exactly caused this deactivation. Was it a click on a different page or a click on the same page.
>
>I now realise, that the only possible solution could be to cover tabs with some other controls (options, for example). This would work, but it brings a level of unwanted complexity...