>>Umm, QueryUnload fires after Destroy??? Gee, that's news to me. Everything I've ever read says it's before.
>
>Haha. In fact, this is the exact line from QueryUnload in the Docs: "The QueryUnload event occurs before the Destroy event."
>
>Is the form based on a class that does some goofy stuff like calling QueryUnload() for some reason in the Destroy()?

Nope! The error is occurring in DisconnectServers which is called from QueryUnload. It's referencing the object that no longer exists (1925 - Unknown member). Destroy (in a bit of programmatic overkill) has set the property to NULL (it's also the only place that this was done). It's not a big deal to remove this from Destroy, since the object will be destroyed anyway, before the form unloads. That's not an issue, it's the goofy sequence.