Bonnie,

Thanks for your response. Of course you are right for most cases...there are some situations where there is really nothing to save (report runs, data lookup screens for example), but the field validation can wait until the query itself is launched for those screens.

The question was something I stumbled upon while playing with control validation.


>
>I looked through the various Form properties and couldn't find anything obvious.
>
>But, I wonder if that's what you really want to do? Typically, when a user clicks on the 'X', they should be asked if they want to save their changes (if there are any, that is) and so I think your validations should still execute. A lot of users click on the 'X' not necessarily as a means of "escaping" the process, but just because it's an easy way to close a form and a lot do it out of habit. I'd hate for them to lose all changes to data on the form without informing them of such.
>