Ummm. Because it has to be activated to know what to query unload?????

Tangentially, I really hate it when I set a breakpoint in the activated method. Break, switch to debugger, murmercursemurmur, switch back to form, fires activate, which....:-) Boy am I glad you can disable breakpoints.

>Interesting - I tried it with a Wait Window and the QueryUnload code seemed to be skipped (the code was updating a table).
>
>It seems that the code up to the Message box is fired BEFORE the activate, then the activate, then the messagebox. In my case, the QueryUnload code was negated by the Activate code < **sigh** >
>
>Truly strange - I can see firing the Activate, but IN THE MIDDLE of the Query Unload?
>
>Barbara
>