>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.

Well, my only thought is, if Destroy() did NOT call QueryUnload(), Destroy() wouldn't show up in the calling stack, it would have finished and VFP would have internally moved on. For example, if you look at the calling stack in the Init() of a form, you probably won't see Load() (Haven't tested it though)

So, its either Dave's idea (but I don't think the calling stack works like that) or that some code in the Destroy calls it.

Wierd...