robert_s wrote: c:\Documents and Settings\user\My Documents\Prog\Prog.exe %1 Is it correct? Be sure and put double-quotes around the %1. robert_s wrote: its a bit silly to have one long string as it will be a hassel to separate one argument from the other as the are blank spaces all over the place so it will be hard to determine where to split it. Can you use the CCommandLineInfo class? If not, __argv[1] is always available. "When I was born I was so surprised that I didn't talk for a year and a half." - Gracie Allen

How are you creating your dialog object? Modal's are (usually) created on the stack (or heap): CMyDialog myDlg; myDlg.DoModal() // Display a modal dialog When it goes out of scope, everything is cleaned up automagically...(if created on the stack) robert_s wrote: Now I am confused as my dialog does not call any of those functions and I am still able to display it. Now I am confused...how are you creating a dialog if your no calling Create or DoModal??? :confused: robert_s wrote: My second question: The dialog I created is used to display a progress bar while some text files are processed using a separate worker thread (thread used purely for files processing not for the dialog). The problem I have is when I start processing files the dialog with the progress bar appears but its behind the main window. How can I force it to display over the main window as the modal dialogs do? I guess WS_OVERLAPPED will do but where to use it? SetForegroundWindow()??? How do I print my voice mail?

Ok thank you. Cwnd::SetIcon() solved my problem :)

robert_s wrote: But still its a bit silly to me to return FALSE. The function name (OnInitiDialog) suggests that I am initializing a dialog... The return value has nothing to with success/failure. It simply denotes whether the application has set the input focus to one of the controls in the dialog box. "The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)