You need to catch the exception and then print out a stack dump to let you know where it crashed. There are some debuggin libraries available on codeproject that will handle stack dumps. Todd Smith

Thanks it's a lot clearer to me now :)

let me guess ur problem: m_pDlg is a pointer to CDialog or its sub-class, say XDialog. instances are not from XDialog, but its sub-class. if my guess is correct, simply change distructor to 'virtual' one. that is all. for MFC class, it is not necessary to call Destroy, MFC can do it itself. includeh10

AS well as articles here, try www.sgi.com for good online docs. Christian I am completely intolerant of stupidity. Stupidity is, of course, anything that doesn't conform to my way of thinking. - Jamie Hale - 29/05/2002 Half the reason people switch away from VB is to find out what actually goes on.. and then like me they find out that they weren't quite as good as they thought - they've been nannied. - Alex, 13 June 2002

I have one rule, if the task may be long or asynchronous operation -> thread [yes] if short task -> thread [no] One good thing about getting older, you don't lose the ages you've been!

Sorry my fault, I have made sure that the message queue has been created properly. This is because the messages inside the queue were correctly being processed. Thanks for picking this up! wilche

Thanks for your reply. Not disputing what you said but I have some questions.... If I used worker thread, for example the following code: //ThreadProc is the procedure used by worker thread int ThreadProc() { // event declarations and def event[0] = ::CreateEvent(NULL, TRUE, FALSE, NULL) // Stop/abort event[1] = ::CreateEvent(NULL, TRUE, FALSE, NULL) // Run DWORD status; while(TRUE) { status = WaitForMultipleObjects(2, event, FALSE, infinite); switch(status) { case WAIT_OBJECT_0: // Abort CloseHandle(ThreadId); return result; case WAIT_OBJECT_0+1: result = RunFunction(); break; } } return result; } In this case, wouldn't it still wait for RunFunction to finish before processing the Abort Event? If I create an UI thread using message queue, I do something similar using GetMessage say. int ThreadProc() { DWORD status; while(TRUE) { status = GetMessage(&msg, NULL, 0, 0); // Check that the message is valid...code ignored here. Assume it's ok switch(msg.message) { case abort: // Abort CloseHandle(ThreadId); return result; case run: result = RunFunction(); break; } } return result; } Would I still have the same problem? In this case, RunFunction will have to be completed before the next message will be processed. Kind regards, wilche

applications could gain quite a bit of responsiveness and performance if they used threading in the right places, for the right reasons and in the right way. This is so true. All too often I see people use threads and then fill the code with sync points (elements of the code where one thread must wait or sync with the other). Perfect threading has no sync points. Realistic threading has a few. Poor threading has the thread constantly syncing. When that happens, what is the real point. Tim Smith I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?

Thank you Ernest! It works great, thanks! Life is like fishing. We are all waiting for a bite

wilche wrote: Is VC++ 7 much different from VC 6? Not really. There are newer classes and functions! But the interface has totally changed. Don't go looking for the class wizard and stuff like that. The GUI takes some adjustment-time Nish :-) Regards, Nish Native CPian. Born and brought up on CP. With the CP blood in him.

delete (char *) msg.wParam; This deletes only 1 char not an array of char. Add [] to delete arrays. The reinterpret_cast<> is a c++ way of casting. John

Thank you Prem for your suggestion. The same message is being sent continously and each message is important to be processed. However, I don't quite understand what you mean by the trailing messages. Could you elaborate on that? :)