So disable the main application window before you show the dialog. A bit of advice - it sounds like you're trying to do some sort of progress / wait dialog. That's fine - this is a good way to go about that. But keep in mind, if you're doing some sort of lengthy processing in your primary (UI) thread, the interface won't respond or repaint while that's happening anyway, since messages won't get pumped. If you have something that is gonna take a while, see if you can't just spin off a separate thread to handle it, posting back status messages or whatever to the main thread. Trust me, it's a lot easier to plan it out and do it right the first time than it is to go back and hack around laziness later... Post faster, post more, post now

Hi Susmita, I could not give you answer still I haven't understood what you do in displaying the text in output view. 1. Is your Output view has OnDraw(...) or OnPaint() message handler to paint your document data on the output view? 2. Clear has different meanings.. Clear the View means do you want to clear the data which is stored in Document object? 3. OR you won't clear the document object content, but do you want to display some background color on the view? For Option 3, what you can do is 1. Have one boolean variable which is funtioning like a toggle 2. When click the button to clear the view, set the bool to true (bClear = true. Now you have to Invalidate the view/window(Which will send WM_PAINT Message and call your OnDraw / OnPaint Message handler) 3. In the OnDraw/OnPaint handler check for the boolean flag (bClear) 4. if bClear is true, then do not call any paint related function Sample Code IMPLEMENT_DYNCREATE(CPaintTestView, CView) BEGIN_MESSAGE_MAP(CPaintTestView, CView) //{{AFX_MSG_MAP(CPaintTestView) ON_COMMAND(ID_VIEW_CLEAR, OnViewClear) ON_UPDATE_COMMAND_UI(ID_VIEW_CLEAR, OnUpdateViewClear) //}}AFX_MSG_MAP // Standard printing commands ON_COMMAND(ID_FILE_PRINT, CView::OnFilePrint) ON_COMMAND(ID_FILE_PRINT_DIRECT, CView::OnFilePrint) ON_COMMAND(ID_FILE_PRINT_PREVIEW, CView::OnFilePrintPreview) END_MESSAGE_MAP() .. .. ... CPaintTestView::CPaintTestView() { m_bClear = false; } ///////////////////////////////////////////////////////////////////////////// // CPaintTestView drawing void CPaintTestView::OnDraw(CDC* pDC) { CPaintTestDoc* pDoc = GetDocument(); ASSERT_VALID(pDoc); if (m_bClear) { } else { pDC->TextOut (20,20,"I Love Bangalore"); } } void CPaintTestView::OnViewClear() { m_bClear = !m_bClear; InvalidateRect(NULL,true); } void CPaintTestView::OnUpdateViewClear(CCmdUI* pCmdUI) { if (m_bClear) { pCmdUI->SetCheck (); } else { pCmdUI->SetCheck (false); } } I hope this will help you.. " Action without vision is only passing time, Vision without action is merely day dreaming, But vision with action can change the world " - Words from Nelson Mandela Thanks & Regards, Gopalakrishnan

Certainly you could pass a message with CDC as parameter - or create custom class to do printing and from the OnPrint method in one of the views create an array of pointers to all other views and pass this as a parameter to your print method that would then print all of them. As per printing accross pages - done it few times and always a headache. One of the better techniques I used was clipping rectangles (per page) and moving CDC drawing origin according to the page being printed. I think this worked the best for me. Good luck :) Regards JP

Thanks so much for your explaination and sample. It reall helped me. One question is : when I do BeginWaitCursor() it shows the hourglass for a fleeting second and again changes back to the arrow cursor. It does not stay as hourglass for the entire lengthy operation. Any help how to fix that?

The short answer: Never mind first-chance exceptions. They are not bugs. They are just what it says: a first chance to handle an exception. They will be send to you to give you an opportunity to handle the exception before the framework gets to it, but I have never seen a case where I needed to deal with a first-chance exception. They will usually be handled quite sufficiently by the framework. The exceptions you get are probably due to memory being allocated but not committed, or memory not being allocated yet. My guess is that OleInitialize uses these exceptions in its memory allocation scheme and that they are part of normal execution. Cheers Steen. "To claim that computer games influence children is ridiculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"

Thanks for all the help. I could accomplish what I wanted to do with all your help. Thank Again