Finally solved it.
On Fri, 30 Jan 2009 09:04:02 -0800, ComtriS
<ComtriS@discussions.microsoft.com> wrote:
I'm still stumped.
Since I posted my reply to you, you've written:
Well, I tried this again. I put the AfxMessageBox at the beginning and
end
of each destructor. When I close the dialog now, it makes multiple
closing
sounds in quick succession -- but not a single message box pops up.
That's exactly the problem I described in my first reply to you. I don't
know of any other cause for this problem, so I can only suggest
double-checking your earlier attempts to apply the workarounds suggested
in
the KB article I cited as well as my alternative. I don't know if it's
possible to have multiple queued WM_QUIT messages, but you might try the
PeekMessage in a loop. (ISTR some messages such as WM_PAINT and WM_TIMER
aren't queued but are instead represented by a flag, and WM_QUIT may or
may
not be the same.)
--
Doug Harrison
Visual C++ MVP